Project

General

Profile

Actions

Feature #27988

open

Option to configure which trackers can be set as subtasks for each tracker

Added by Marius BĂLTEANU almost 7 years ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Category:
Issues workflow
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

A few months after we started using Redmine in Zitec, we developed the Redmine Restrict Tracker plugin which allows us to configure which trackers can be set as subtasks for each tracker.

Why we did the plugin?
We started with the following standard (for Agile development) trackers:
1. Epic
2. User Story
3. Task
4. Bug

After a few months, we observed a lot of mistakes made by our users: Epics having subtasks another Epics, Tasks having subtasks User Stories and so on.
Then we decide to create this plugin to restrict the subtasks to specific relations: Epics only with User Story trackers as subtasks, User Story only with Task and Bug trackers as subtasks, etc..

Current settings
The current workflow settings allows you to configure only if a tracker can/must be or not a subtasks (by making the field Parent task Read only, Required or Optional).

Because I find this feature very useful and a missing piece from the already powerful workflow settings, I've started work to a patch that implements this feature in the following way (different by the implementation from the plugin which has his own issues):


According to the settings from the image, the Feature tracker can have as subtasks only issues with Bug and Support trackers.

Please let me know what you think about this feature and the proposed implementation.


Files


Related issues

Related to Redmine - Feature #29470: Possibility to mark tracker as "Subtask only"ReopenedJean-Philippe Lang

Actions
Actions

Also available in: Atom PDF