Description for issue statuses
We have the problem that users are not always sure what the semantic of a certain status is and what status they should set for a ticket when updating it.
Therefore it would be nice to be able to add a documentation to issue statuses, especially when introducing custom statuses. The documentation could then be presented to the user as a tooltip when selecting a status for a ticket.
#4 Updated by Thomas Woelfle almost 13 years ago
Thomas Pihl wrote:
Why not just document them on the wiki?
I have a page for each of those (incl some custom fields as well)
That's what we are doing currently. Some of our developers mentioned that it would increase the usibility if they do not have to open one or more wiki pages (for statuses, categories, priorities, ...) while creating or updating issues.
Well, as said, it is just a usibility feature request.
#6 Updated by Dipan Mehta over 8 years ago
+1 This is very important. Usually, when reading in a wiki you read things like reading a book - you don't know what to search for where. When people are in the 'act of doing things' it makes sense to give them tool tip or some contextual help which doesn't requires them to move around pages. This is very very crucial!
The closest to this I had came across - is extended fields which provides Hint per field. Again, this doesn't help about core fields, and also it is not sufficiently contextual i.e. different for each tracker/status to tell users "what they should write HERE and NOW!"
#14 Updated by Dipan Mehta over 8 years ago
Another related #5026 - requires description/documentation for Status/Role/Tracker.
Looks like, there is a lot of demand for the 'instant end-user documentation'