bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Kitchin <>
Subject Re: User comments on ticket modification UI
Date Thu, 31 Jan 2013 22:00:06 GMT

I've been following along in the discussion and I've been encouraged to
weigh in, so I've just spent a bit of time playing with the ticket layout,
and my thoughts are below.

My first thought is that the scroll spy doesn't really suit the layout, as
has been suggested - on my laptop at least it takes up a considerable
amount of screen estate without providing much value - the ticket itself
simply isn't long enough to warrant it.  As has also already been noted,
the "Modify ticket" button also functions differently from the line of
similarly styled buttons next to it.  It might work better if the Modify
ticket button was visibly separated from the positional buttons, and became
the Update/Submit/whatever button when in edit mode instead of having the
"Update (leave)" button above it.  This would cut back on the size of the
spy a bit without losing functionality.  The length of the change history
isn't a problem if the spy is kept this way, as well - collapsing it
strikes me as a bit clunky.

I think there's a strange overlap on changes to comments.  I agree that any
change should allow for leaving a comment with it, but then we have a
section called "Change history" in the page but "Comments" in the spy, and
the "Submit changes" button being used to submit a comment even if you're
not in edit mode.  We should encourage discussion of tickets where
relevant, so making commentary without change easy would be best, I think.
 Perhaps just reducing the "Submit changes" text of the button under the
comments box to "Submit" would be enough of a change there?  I suspect that
a comments box on a ticket with "Submit changes" under it would make me
nervous, while just "Submit" reads as submitting a comment when commenting
and submitting changes when editing.  Similarly, the Comments navigation
button could read "History" instead, which I think also carries a dual
meaning which will make sense to people looking for past comments and
people looking for the change history.

I think accept/reassign/resolve should be buttons outside of edit mode, and
should act immediately rather than need submitting.  If they're a set of
actual buttons their purpose and immediate effect is completely clear,
while embedding them in the Update button dropdown is confusing.  Unless
you check the dropdown, what does "Update (leave)" mean, anyway?


On 31 January 2013 16:45, Joachim Dreimann <>wrote:

> I'm keen to see the changes Matevz will propose in his responsive layout
> patch. I'll wait until then to make up my mind on the changes.
> - Joe
> On 30 January 2013 04:34, Olemis Lang <> wrote:
> > On 1/29/13, Matevž Bradač <> wrote:
> > >
> > [...]
> > >
> > > On another note, some fields (such as Reporter for example) shouldn't
> be
> > > editable IMO,
> > > as this modifies the ticket history. I suppose this is not something
> > > desirable.
> > >
> >
> > AFAICR only TRAC_ADMIN is allowed to do so . I've seen some instances
> > when this was necessary @ t.e.o
> >
> > --
> > Regards,
> >
> > Olemis.
> >
> > Blog ES:
> > Blog EN:
> >
> > Featured article:
> >
> --
> Joe Dreimann
> UX Designer | WANdisco <>
> *
> *
> *Transform your software development department. Register for a free SVN
> HealthCheck <> *

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message