Issue300

Title explain status values directly in bug edit form
Priority bug Status chatting
Superseder Nosy List loewis, techtonik
Assigned To Topics

Created on 2009-09-17.12:17:18 by techtonik, last changed 2009-09-20.18:52:40 by techtonik.

Messages
msg1474 (view) Author: techtonik Date: 2009-09-20.18:52:40
About this tracker instance.
msg1471 (view) Author: loewis Date: 2009-09-18.07:15:48
Which specific bugtracker are you talking about? bugs.python.org has only three 
status fields (Open, Closed, Pending); they do have explanations.
msg1469 (view) Author: techtonik Date: 2009-09-17.16:08:11
Need to rephrase this.

In bug edit form Status field should have accessible explanation for users.
msg1466 (view) Author: loewis Date: 2009-09-17.15:11:33
Please elaborate: possible for whom?
msg1462 (view) Author: techtonik Date: 2009-09-17.12:17:17
It should be possible to provide descriptions for Status fields directly in edit 
form, like a popup hint on hovering mouse.

http://www.nabble.com/Meaning-of-status-abbreviations-need-eg,-done-cbb-
td2537614.html
History
Date User Action Args
2009-09-20 18:52:40techtoniksetmessages: + msg1474
2009-09-18 07:15:49loewissetmessages: + msg1471
2009-09-17 16:08:11techtoniksetmessages: + msg1469
2009-09-17 15:11:33loewissetstatus: unread -> chatting
nosy: + loewis
messages: + msg1466
2009-09-17 12:17:18techtonikcreate