Redmine

+1
I would also really appreciate this feature.

The same would be nice for categories and priorities too.

Why not just document them on the wiki?

I have a page for each of those (incl some custom fields as well)

/T

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)

/T

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.

If you could attach a description to each status/category/priority then it could be displayed as a tooltip, vs having to look it up on the wiki.

+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!"

This could be solved too by a new look of the issue generation.
Maybe I could provide a new issue assistent the coming weeks.

Why is the category documentation? The feature is actually asking for 'Tooltip/Hint/Help framework based on context' in Redmine.

Issue #442 talks about contextual documentation of Tracker rather than Status or custom fields However, we can have generic frameworks that can encompass all such contextual help/documentation aspects.

Add related #9256 - the framework of #2568 essentially will cover that.

Another related #4768 - essentially documenting and contextually describing 'Category' (e.g. what type of issues qualify for this category) is another important example.

Another related #5026 - requires description/documentation for Status/Role/Tracker.

Looks like, there is a lot of demand for the 'instant end-user documentation'

I was wondering, while issue #9256 is already planned under Candidate for next major release, will it be a good idea to have #2568 in the same release?

+1

db/migrate/20230818020734_add_status_description.rb of the patch is missing in the commit.

Alexander Meindl wrote in #note-24:

db/migrate/20230818020734_add_status_description.rb of the patch is missing in the commit.

Thank you, fixed in r22290.