We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 433
    • 99
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update – 4 January 2016

      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.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 433
              • 99
              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

                Atlassian Update – 4 January 2016

                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.

                        Unassigned Unassigned
                        b1f0ea1989c1 Mark Hetherington
                        Votes:
                        850 Vote for this issue
                        Watchers:
                        401 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            b1f0ea1989c1 Mark Hetherington
                            Votes:
                            850 Vote for this issue
                            Watchers:
                            401 Start watching this issue

                              Created:
                              Updated: