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

remove sub-tasks as a unique issue type -- sub-tasks should represent a relationship, not an issue type

    XMLWordPrintable

    Details

    • UIS:
      2
    • Support reference count:
      2
    • 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.

      Description

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

      Atlassian Update - 23 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. David's description here is in line with the JIRA PM team's current thinking about subtasks. We want to strike a balance between more flexible parent-child hierarchies and the reasoning in Scott's original comment that having separate issue types allows for different sets of fields in the subtask.

      Nevertheless, I don't expect us to address this for quite a while. We will update this issue as soon as we can confidently project a release.

      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

      To create what should be a simple parent-child relationship between 2 issues in JIRA, you need to define a UNIQUE sub-issue type for every single type of child issue you might want.

      So lets say I have existing issue types Dev Task, Ops Task, Future Planning, QA Task, Documentation. And I want to create a parent Documentation issue that has sub-issues for each of my depts that will be contributing: Dev Task, Ops Task, QA Task. I now have to create a whole new sub-issue ("sub-task") type for each of these just so I can create a proper parent child relationship between my parent issue and sub-issues. And for each sub-issue, I have to duplicate all my previous work on the main issue types with similar names and assign all the right field configs/screens/etc, and when searching for Eng Tasks, I now have to search for both Eng Tasks and Eng Sub-Tasks.

      Lets get rid of the concept of "sub-tasks" entirely, and express parent-child relationships between issues as just that – defining a relationship – not entirely new issue types.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              arsenale David Goldstein
              Votes:
              60 Vote for this issue
              Watchers:
              44 Start watching this issue

                Dates

                Created:
                Updated: