UI
avatar mbabker
mbabker
29 Nov 2013

Realizing most don't have access to the edit view on the live site (I think there's 5 people total?), few probably realize that it's there or how it is definitely built by developers. So here's a screenshot for those who haven't done a local setup, anyone want to improve this?

j tracker 237

avatar mbabker mbabker - open - 29 Nov 2013
avatar brianteeman
brianteeman - comment - 29 Nov 2013

What is the Number field?
You may blame the J!Tracker Application for transmitting this comment.

avatar mbabker
mbabker - comment - 29 Nov 2013

Part of our inbuilt issue relation tracking, associated with the type field next to it. Totally not clear, I know.

avatar brianteeman
brianteeman - comment - 29 Nov 2013

I would start by moving the Save and Cancel buttons from the subnav to the breadcrumbs
Just as we moved the edit button
You may blame the J!Tracker Application for transmitting this comment.

avatar elkuku
elkuku - comment - 30 Nov 2013

What is the Number field?

It starts to make sense when you select a "Type" like
relation-number
Totally not clear, I know.
Not sure if we're going with this approach, use the GitHub "references" or even labels ?

Moving the Save and Cancel button sounds good - I think we need some "common area" where to place those buttons. Breadcrumb just doesn't feel right... but I think that's the choice for now.

avatar elkuku elkuku - reference | - 30 Nov 13
avatar brianteeman
brianteeman - comment - 30 Nov 2013

Thinking about it now and how the two fields are connected to each other and how best to express that within the ui

How about changing the field labels to this
screen shot 2013-11-30 at 10 14 30

And increasing the "gap" between the previous fields to visually indicate that these two fields are connected and separate to the others

screen shot 2013-11-30 at 10 30 00

avatar elkuku
elkuku - comment - 30 Nov 2013

Sounds good. My only concern is that the tracker might be a "Feature tracker" (can a feature be related to another ? ...) so maybe we should put "Item" instead of "Issue" ?
As always - not sure about the wording...

Off Topic
I'd like to quote @eddieajau from another thread here (and this is not - in any way - meant as an offense !)

@brianteeman: Please clone yourself, we need more of you.

avatar brianteeman
brianteeman - comment - 30 Nov 2013

Yes a feature can be related as the PR would be related to the issue
You may blame the J!Tracker Application for transmitting this comment.

avatar HermanPeeren
HermanPeeren - comment - 30 Nov 2013

What if a ticket is related to several issues?

avatar elkuku
elkuku - comment - 30 Nov 2013

What if a ticket is related to several issues?

That can be considered a limitation but it also depends on what the relation actually is. I mean a "duplicate" can not be a duplicate of another.
The feature is also meant as an aid, so that you can focus on one issue (where the "related children" will be displayed)

I tried to explain the limited possibilities in #76 and I think there is a lot of space for improvements ;)

avatar elkuku elkuku - reference | - 2 Dec 13
avatar b2z
b2z - comment - 11 Feb 2014

Moving the Save and Cancel button sounds good - I think we need some "common area" where to place those buttons. Breadcrumb just doesn't feel right... but I think that's the choice for now.

For me it's very suitable place.

avatar b2z
b2z - assign - 22 Oct 2014
Assigned to b2z
avatar b2z b2z - close - 12 Dec 2014
avatar b2z b2z - close - 12 Dec 2014
avatar b2z b2z - change - 12 Dec 2014
Status New Closed
Closed_Date 0000-00-00 00:00:00 2014-12-12 12:26:58

Add a Comment

Login with GitHub to post a comment