Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-8063

Board option for allowing sub issues to be treated as other issues

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • AgileBoard
    • None
    • 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.

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

      The Atlassian way of handling sub issues is to only calculate their workload using time estimates. This is not how all teams work, and it would be nice to have an option on the board that lets you set if sub issues should be treated just like any other issue. This would broaden up the use of the rapid board for more of its users.

      One problem with the current implementation is that story points on sub issues are not shown in the burndown chart. Any subissue is not shown in these charts at all. This makes statistics gathering somewhat hard to do if you treat issues in this way.

      An added bonus would be if the combined value of the story points could be viewed on the parent issue as a calculated field. This calculated fields should not count towards the statistics of course.

            [JSWSERVER-8063] Board option for allowing sub issues to be treated as other issues

            Leif Rask added a comment -

            Not good.  A valid use-case for sub-tasks is failed tests or related bugs arising while testing an issue. These should be child issues and also visible on the board for workflow resolution. Having them hidden inside the parent issue obscures the current state of developments underway. 

            At the moment, we have to create separate issues and "link" them back to the parent issue as a "relates to" or "blocks". In this manner, sub-tasks are a pointless feature.

            Another valuable use-case for sub-tasks is tests to be conducted for an issue. It truly astounds me that Jira doesn't have any workflow for testing as part of issue tracking and resolution.

            (I really wonder sometimes if Jira people actually use their own software)

            Leif Rask added a comment - Not good.  A valid use-case for sub-tasks is failed tests or related bugs arising while testing an issue. These should be child issues and also visible on the board for workflow resolution. Having them hidden inside the parent issue obscures the current state of developments underway.  At the moment, we have to create separate issues and "link" them back to the parent issue as a "relates to" or "blocks". In this manner, sub-tasks are a pointless feature. Another valuable use-case for sub-tasks is tests to be conducted for an issue. It truly astounds me that Jira doesn't have any workflow for testing as part of issue tracking and resolution. (I really wonder sometimes if Jira people actually use their own software)
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3068724 ] New: JAC Suggestion Workflow 3 [ 3662251 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2625461 ] New: JAC Suggestion Workflow [ 3068724 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2322743 ] New: Confluence Workflow - Public Facing v4 [ 2625461 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2040807 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2322743 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2027195 ] New: JIRA PM Feature Request Workflow v2 [ 2040807 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736544 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2027195 ]
            jonah (Inactive) made changes -
            Description Original: The Atlassian way of handling sub issues is to only calculate their workload using time estimates. This is not how all teams work, and it would be nice to have an option on the board that lets you set if sub issues should be treated just like any other issue. This would broaden up the use of the rapid board for more of its users.

            One problem with the current implementation is that story points on sub issues are not shown in the burndown chart. Any subissue is not shown in these charts at all. This makes statistics gathering somewhat hard to do if you treat issues in this way.

            An added bonus would be if the combined value of the story points could be viewed on the parent issue as a calculated field. This calculated fields should not count towards the statistics of course.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSWCLOUD-8063].
              {panel}

            The Atlassian way of handling sub issues is to only calculate their workload using time estimates. This is not how all teams work, and it would be nice to have an option on the board that lets you set if sub issues should be treated just like any other issue. This would broaden up the use of the rapid board for more of its users.

            One problem with the current implementation is that story points on sub issues are not shown in the burndown chart. Any subissue is not shown in these charts at all. This makes statistics gathering somewhat hard to do if you treat issues in this way.

            An added bonus would be if the combined value of the story points could be viewed on the parent issue as a calculated field. This calculated fields should not count towards the statistics of course.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSWCLOUD-8063 [ JSWCLOUD-8063 ]
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 515106 ] New: JIRA PM Feature Request Workflow v2 [ 736544 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

              Unassigned Unassigned
              d0deb58a156e Stig Runar Vangen
              Votes:
              13 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: