Hi Joe, I apologize for not communicating this more clearly.
The main reason for the changes was to make it more usable across all devices, not just desktops. To make that work, the following "goals" should be met (in my opinion, that is): - All, or at least most of the change information should be directly visible, without any need for user interaction (e.g. hovering over changes to display the date information is not a viable option for tablet/phone users) - The user should be able to quickly tell for each change what exactly was changed, who made the change and when - the visual clues hopefully achieve that goal. - The information should be presented in compact form, but not to the point of losing readability across different devices. As for the comments, I do understand they should be made more visually distinct and I'm still working on that. Additionally, there are ticket changes which include both property and comment changes, and those should be addressed as well. All the recent commits I've made wrt. the ticket page are marked with #533. If you feel the changes are too intrusive and/or do not function as they should, please let me know and I'll revert them back to the previous layout. And apologies again for not discussing this first on the devlist. Cheers, matevz On 29. May, 2013, at 19:08, Joachim Dreimann wrote: > Thanks for fixing the placement of the ticket details and some of the other > stuff Matevz. > > In the change history comments left by users were visually distinct from > other ticket changes, such as ticket detail field changes. That's because I > reasoned that comments would be more important to users than field changes, > making the latter less prominent. > > There appear to have been some major changes recently to the way the change > history looks on ticket pages. They seem like a regression to me. I didn't > find them mentioned in the commit messages or this ticket (#533) either, > but I may have missed something of course. > > What was the reason for this change? > > I'm not certain at which revision this change was made, but here is a > comparison: > > Trunk: > https://issues.apache.org/bloodhound/attachment/ticket/533/NewTimelineScreenshot.png > > r1485261: > https://issues.apache.org/bloodhound/attachment/ticket/533/OldTimelineScreenshot.png > > Cheers, > Joe > > > On 24 May 2013 12:33, Apache Bloodhound <[email protected]> wrote: > >> #533: Ticket page cleanup >> ----------------------------------------------+----------------------- >> Reporter: matevzb | Owner: matevzb >> Type: defect | Status: new >> Priority: major | Milestone: Release 6 >> Component: dashboard | Version: 0.5.3 >> Keywords: ticket page, properties, details | >> ----------------------------------------------+----------------------- >> This ticket is closely related to #520, with further small improvements: >> - Move the ticket details back to the top, add a heading. The reason for >> this is that the ticket description can be very long in some cases, >> obscuring the detail fields from view (e.g. https://bh- >> demo1.apache.org/products/%40/ticket/513). >> - Ticket Details modifications: lighter, left-aligned field labels seem to >> make the details more readable. >> - Separate the Details and Description sections from Attachments, >> Relations etc., using a smaller heading (h4). The former are ticket >> properties, the latter are not and are also managed/edited separately. >> >> There are other areas in need of improvement, such as: >> - Intuitiveness of the "Modify ticket" action: the "Submit changes" and >> "Cancel" button are placed on the top of the form, which feels awkward to >> use. Additionally the semantics of "Submit changes" and the "Submit" >> button in the comments is not clear in the ticket editing mode (i.e. which >> button does what?) >> - Create ticket (full form) now has the "Create ticket" button and the "I >> have files to attach" checkbox positioned on the top-right side of the >> page, instead of the end of the form. >> - etc. >> >> -- >> Ticket URL: <https://issues.apache.org/bloodhound/ticket/533> >> Apache Bloodhound <https://issues.apache.org/bloodhound/> >> The Apache Bloodhound issue tracker >> > > > > -- > Joe Dreimann | *User Experience Designer* | WANdisco<http://www.wandisco.com/> > > @jdreimann <https://twitter.com/jdreimann>
