Patch #27219
closed
Show default status on the trackers list
Added by Tomomi Yuzuriha over 6 years ago.
Updated over 6 years ago.
Description
I noticed a problem when trying to delete a status.
An user cannot delete a status if the status is set to 'Default status' of some tracker.
Nevertheless, there is no way to know which tracker uses the status as a default status except for each tracker's edit page.
if you register a lot of trackers, it is very hard to check the default status.
To resolve the problem, I suggest showing the default status on the trackers list.
With this small improvement, users can see the default status of all trackers at a glance.
Please see the screenshot below for the details.
Patch: trackers_index_trunk_r16967.patch
(Compatible the latest trunk r16967.)
Files
- Target version set to Unplanned backlogs
Tomomi Yuzuriha wrote:
An user cannot delete a status if the status is set to 'Default status' of some tracker.
Nevertheless, there is no way to know which tracker uses the status as a default status except for each tracker's edit page.
if you register a lot of trackers, it is very hard to check the default status.
This seems to be a valid, real-world issue.
To resolve the problem, I suggest showing the default status on the trackers list.
With this small improvement, users can see the default status of all trackers at a glance.
This is IMO a neat solution to the given problem. Setting target to 'unplanned'.
Mischa, I think we can merge this tiny improvement without any harm and side effects. I would like to set target version to 4.1.0. Is it OK with you?
- Target version changed from Unplanned backlogs to 4.1.0
Go MAEDA wrote:
[...] I would like to set target version to 4.1.0. Is it OK with you?
Ok for me. I change the target version to 4.1.0.
I think showing default status on trackers page improves consistency because API for trackers (GET /trackers.xml) already returns default_status since Redmine 3.0.0 (see Rest_Trackers).
- Status changed from New to Closed
- Assignee set to Go MAEDA
- Target version changed from 4.1.0 to 4.0.0
Committed the patch in r17140. Thank you for reporting and fixing this issue.
Also available in: Atom
PDF
Updated by 
Updated by