Roundup Tracker - Issues

Message4649

Author rouilj
Recipients rouilj, sqz
Date 2012-09-13.13:24:37
Message-id <201209131324.q8DDOGmU002054@mx1.cs.umb.edu>
In-reply-to Your message of "Thu, 13 Sep 2012 11:23:55 -0000." <1347535435.45.0.649588360548.issue2550777@psf.upfronthosting.co.za> <1347535435.45.0.649588360548.issue2550777@psf.upfronthosting.co.za>
In message <1347535435.45.0.649588360548.issue2550777@psf.upfronthosting.co.za>
 <1347535435.45.0.649588360548.issue2550777@psf.upfronthosting.co.za>,
Coder of Salvation writes:
>html/issue.item.html
>====================
><textarea tal:content="request/form/@note/value | default"
>            name="@note" wrap="soft" rows="5" cols="80"></textarea>
>
>(I changed the wrap="hard" to wrap="soft", and in combination with the 
><pre> stylesheet-settings, it wont break long urls, because then they 
>become unclickable, and also it will prevent the 'search'-field 
>dissappearing from the screen which happened with long content)

Hmm, I never saw the search box dissapear. I have had to scroll to get
to it on occasion though. What browser were you using that removed the
search box based on line wrap for the note field?

>The edit button
>===============
>Attached is my issue.item.html which initally hides the form-fields 
>behind a big Edit-button. I had to do this because else issues looked 
>too complex for my nontech-clients. After using it for almost a year, I 
>can say Im really used to it, and I think the experience is much more 
>calmer now. Think about it: first information, then editing-forms :)

If this is to be included we need to make it an option settable from
tracker.ini. RT and some other ticketing systems use this same view
and oinly then edit model. That means you can't start editing as soon
as the ticket is pulled up. You have to wait for a another round trip
to the server to render the ticket in a form that is useful. It really
is a pain and slows down ticket management IMO.

The number of fields that an average user can change (and therefore
are in edit mode) is usually much less than that of the person
responding to/managing the ticket. I have never had an issue with
users being confused by the edit fields.

But I can see it being a valid use case, I just think it makes for a
poor work flow so should be optional and controllable on a per tracker
basis by an option (rather than having to cut the code out of the
template).
History
Date User Action Args
2012-09-13 13:24:37rouiljsetrecipients: + rouilj, sqz
2012-09-13 13:24:37rouiljlinkissue2550777 messages
2012-09-13 13:24:37rouiljcreate