[#JRA-7990] Restrict sub-tasks by issue type

JIRA

Restrict sub-tasks by issue type

Created: 19/Sep/05 02:17 AM Updated: 26/May/08 06:18 AM

Component/s:

Sub-tasks

Affects Version/s:

3.3.1

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue is related to:

~~JRA-11125~~ JIRA 4.0 Enterprise Requirements

Participants:	Mark Hetherington, Roy Krishna [Atlassian] and Tibor Hegyi
Since last comment:	14 weeks, 4 days ago
Support reference count:	3
Labels:

Description

« Hide

In a similar way that ~~JRA-1602~~ will restict the issue types for a project, it would be great to be able to restict sub-tasks by issue type. We have plenty of cases where certain subtasks are invalid or meaningless for certain issue types.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Roy Krishna [Atlassian] - 08/Apr/08 11:30 PM

From a customer that would like to raise this as a feature request:

When I click the create sub-task you get a list of all subtasks defined in the system, the problem is that you allow users to choose any type of sub-task although you expect them to use only one sub-task for the current parent issue type. I tried to use the issue type scheme to create a scheme that includes only the sub-task I want but it is mandatory to have at least one standard issue type in scheme.

[ Permlink | « Hide ]

Tibor Hegyi - 09/Apr/08 03:33 AM

I know it is just a workaround, but using an appropriate workflow validator, one can restrict creating sub-tasks per parent issue type.
I have created similar validators with user-friendly configuration screens where these kind of restrictions can be phrased.

As we all know, validators are executed on transitions. This means that the check for sub-task type can be done when user clicks "create" in the Create Issue screen.

Tibor