Project

General

Profile

Actions

Feature #2568

closed

Description for issue statuses

Added by Thomas Woelfle about 15 years ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Issues
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

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.


Files


Related issues

Related to Redmine - Feature #705: Wiki links on field namesNew2008-02-21

Actions
Related to Redmine - Feature #442: Add a description for trackersClosedJean-Philippe Lang

Actions
Related to Redmine - Feature #366: Custom field for issue statusClosed

Actions
Related to Redmine - Feature #4768: "issue category" should have a "description" fieldNew2010-02-08

Actions
Related to Redmine - Feature #5026: Description field for Status/Role/Tracker setting.New2010-03-10

Actions
Has duplicate Redmine - Feature #12002: I'd like to see an Issue Status DescriptionClosed

Actions
Has duplicate Redmine - Feature #35509: Description of issue statusesClosed

Actions
Actions #1

Updated by Jerome Vanthournout about 15 years ago

+1
I would also really appreciate this feature.

Actions #2

Updated by Thomas Woelfle about 15 years ago

The same would be nice for categories and priorities too.

Actions #3

Updated by Thomas Pihl about 15 years ago

Why not just document them on the wiki?

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

/T

Actions #4

Updated by Thomas Woelfle about 15 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)

/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.

Actions #5

Updated by Brad Mace over 14 years ago

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.

Actions #6

Updated by Dipan Mehta almost 11 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!"

Actions #7

Updated by Daniel Felix almost 11 years ago

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

Actions #8

Updated by Toshi MARUYAMA almost 11 years ago

  • Category set to Documentation
Actions #9

Updated by Dipan Mehta almost 11 years ago

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

Actions #10

Updated by Dipan Mehta almost 11 years ago

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.

Actions #11

Updated by Toshi MARUYAMA almost 11 years ago

  • Category deleted (Documentation)
Actions #12

Updated by Dipan Mehta almost 11 years ago

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

Actions #13

Updated by Dipan Mehta almost 11 years ago

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

Actions #14

Updated by Dipan Mehta almost 11 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'

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?

Actions #15

Updated by Mischa The Evil over 10 years ago

  • Related to deleted (Feature #9256: Trackers have a description in addition to a name)
Actions #16

Updated by Toshi MARUYAMA over 9 years ago

  • Category set to Issues
Actions #17

Updated by Toshi MARUYAMA over 9 years ago

  • Has duplicate Feature #12002: I'd like to see an Issue Status Description added
Actions #18

Updated by Go MAEDA almost 4 years ago

  • Subject changed from Issue status documentation to Description for issue statuses
Actions #19

Updated by Go MAEDA over 2 years ago

Actions #20

Updated by Jonas De Meulenaere 8 months ago

+1

Actions #21

Updated by Takenori TAKAKI 6 months ago

+1
I've created a patch to add descriptions to issue statuses.
With this patch, users can set statuses while viewing descriptions, just like with the tracker.

Actions #22

Updated by Go MAEDA 6 months ago

  • Target version set to 5.1.0

Setting the target version to 5.1.0.

Actions #23

Updated by Go MAEDA 6 months ago

  • Status changed from New to Closed
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the patch. Thank you.

Now each issue status has a description field you can see them on the issue new/edit form.

Actions #24

Updated by Alexander Meindl 6 months ago

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

Actions #25

Updated by Go MAEDA 6 months ago

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.

Actions #26

Updated by Mischa The Evil 4 months ago

  • Start date deleted (2009-01-23)
Actions

Also available in: Atom PDF