Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-7990

Restrict sub-tasks by issue type

    XMLWordPrintable

    Details

    • UIS:
      432
    • Support reference count:
      31
    • Feedback Policy:
      We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.
    • Current Status:
      Hide
      Atlassian Update – 6 March 2018

      Hi everyone,

      Thank you for your interest in this issue.

      While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. 

      I understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, including:

      • Performance and stability improvements
      • Archiving projects for improved performance
      • Optimising the use of custom fields
      • Improving performance of boards
      • Improving Jira notifications
      • Allowing users to edit shared filters and dashboards
      • Mobile app for Jira Server 

      We recommend checking out the following apps on the Atlassian Marketplace:

      For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

      Thanks again.

      Regards,

      Jira Server product management

      Show
      Atlassian Update – 6 March 2018 Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.  I understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server  We recommend checking out the following apps on the Atlassian Marketplace: Jira Misc Workflow Extensions Power Scripts for Jira Script Automation Issue Type Filters Workflow Essentials for Jira   For more context, check out our Community blog on  our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Server product management

      Description

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

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              mlh Mark Hetherington
              Votes:
              680 Vote for this issue
              Watchers:
              328 Start watching this issue

                Dates

                Created:
                Updated: