[development] Issue page suggestions

Dries Buytaert dries.buytaert at gmail.com
Sat Nov 10 08:37:45 UTC 2007

Hello Chad and Derek,

after a number of days of actively using the project module changes, I  
have some first feedback.

- You did some impressive work.  :)

- The comment form, however, is a mess -- both visually and usability- 
wise.  Using it continues to feel awkward.  Specifically, I would like  
to make the following suggestions:

     a. The netsed fieldsets for the issue settings (i.e. 'Project  
information' and 'Issue information') drive me crazy.  There is no  
need for the nested fieldsets as the title of the inner fieldsets add  
very little value.  Can we remove the nested fieldsets but keep the  
form elements?  Thanks.

     b. The 'attach new file' fieldset could be collapsed.  Often  
times, you don't attach a file.  I don't feel strongly about this;  
it's minor.  Feel free to leave it as is, if you feel strongly about  

     c. The issue settings should be above the textarea for the  
comment bottom.  Having them on the bottom doesn't work for me.  The  
reason is that I find myself using the issue settings to get an  
overview of the current status of the issue.  I don't always change  
these settings, but I *always* find myself *reading* them before I  
comment on the issue.  You might expect people to scroll up to read  
the status of the issue, but that's not what I'm doing.  Putting the  
issue settings above the comment textarea would make it flow better,  
and make things easier for me.

- The fact that you can add a comment/follow-up without having to  
click a 'follow-up link' is a nice improvement.  Good idea.

Can we try to tweak it a bit and try using a tweaked version for a  


Dries Buytaert  ::  http://www.buytaert.net/

More information about the development mailing list