NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future.
Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
Original description
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.
- is duplicated by
-
JRACLOUD-33809 Sub-task type association with parent-task type
- Closed
- is related to
-
JRACLOUD-40978 Set Default Subtask Issue Type
- Closed
-
JRASERVER-7990 Restrict sub-tasks by issue type
- Not Being Considered