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

Sub-Task in a sprint

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • Hide
      Atlassian Status as at 31 December 2015

      This is a duplicate of GHS-5797.
      A separate issue GHS-7992 tracks the Suggestion for showing sub-tasks in the Backlog (plan mode).

      Kind regards,
      Martin
      JIRA Software

      Show
      Atlassian Status as at 31 December 2015 This is a duplicate of GHS-5797 . A separate issue GHS-7992 tracks the Suggestion for showing sub-tasks in the Backlog (plan mode). Kind regards, Martin JIRA Software
    • 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.

      Have the ability to have Sub-Task included in a sprint without having its parent and siblings included in a sprint.

        1. shot_161213_194042.png
          72 kB

          Form Name

            [JSWSERVER-6825] Sub-Task in a sprint

            Michael Schmettkordt made changes -
            Comment [ Hi, we are implementing SAFe and we use sub-tasks in capabilities & features to bring them to DoR. As we work with scrum e.g. also in legal department, sub-tasks like “legal check” for DoR need to be assigned to a Sprint within the legal team.

            Hope this is a reason to get this issue solved soon. ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3066147 ] New: JAC Suggestion Workflow 3 [ 3661766 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]

            Alexandre de Joncaire Narten added a comment -

            Hello. This software is good. Very good even. However, I have to agree that lacking this feature really makes planning a mind boggle.

            It is highly important that we can create and view sub-tasks of stories/tasks in the backlog view, separately from the parent issues themselves, in order to set them into their own sprints. Some user stories require a few tasks that all together take more than a one or two week sprint. What is the verdict on this feature? Are you looking into making this possible?

            Alexandre de Joncaire Narten added a comment - Hello. This software is good. Very good even. However, I have to agree that lacking this feature really makes planning a mind boggle. It is highly important that we can create and view sub-tasks of stories/tasks in the backlog view, separately from the parent issues themselves, in order to set them into their own sprints. Some user stories require a few tasks that all together take more than a one or two week sprint. What is the verdict on this feature? Are you looking into making this possible?
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2621547 ] New: JAC Suggestion Workflow [ 3066147 ]

            Janani SriGuha added a comment -

            +1 Not having this, or being unable to have a way to move linked tasks together, is causing a ton of overhead. Alternatively would be good to group the Kanban by sprints. Blocking this workflow + blocking all alternatives is just making the software not usable for planning.

            Janani SriGuha added a comment - +1 Not having this, or being unable to have a way to move linked tasks together, is causing a ton of overhead. Alternatively would be good to group the Kanban by sprints. Blocking this workflow + blocking all alternatives is just making the software not usable for planning.
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2320321 ] New: Confluence Workflow - Public Facing v4 [ 2621547 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]

            Bruce Cowley added a comment -

            Reminds me of the now infamous: https://jira.atlassian.com/browse/JSWCLOUD-9167

            Fundamentally, Jira has made some what I'll charitably describe as "odd" architectural decisions:

            They designed the ability to split Epics into Stories and allow summing of said Stories' metrics in the Epic, they designed the ability to split Stories into sub-tasks and allow summing of said Sub-tasks metrics in the Story, which would rationally imply a 3 tier hierarchy system.... but no.

            They provide no pass-through ability to pull through the levels up to the parent level . There's a complete disconnect between the 2 spheres.... unless you're willing to buy expensive add-on products which only fill in some gaps. That's BAD design: you give rational, intuitive sub-divisions for people to use, and invest their time and data in, but then provide no ability to cross-reference and collate the data. What kind of rational project management paradigm is that!?

            Bruce Cowley added a comment - Reminds me of the now infamous: https://jira.atlassian.com/browse/JSWCLOUD-9167 Fundamentally, Jira has made some what I'll charitably describe as "odd" architectural decisions: They designed the ability to split Epics into Stories and allow summing of said Stories' metrics in the Epic, they designed the ability to split Stories into sub-tasks and allow summing of said Sub-tasks metrics in the Story, which would rationally imply a 3 tier hierarchy system.... but no. They provide no pass-through ability to pull through the levels up to the parent level . There's a complete disconnect between the 2 spheres.... unless you're willing to buy expensive add-on products which only fill in some gaps. That's BAD design: you give rational, intuitive sub-divisions for people to use, and invest their time and data in, but then provide no ability to cross-reference and collate the data. What kind of rational project management paradigm is that!?
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2039802 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2320321 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2028329 ] New: JIRA PM Feature Request Workflow v2 [ 2039802 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736907 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2028329 ]

              Unassigned Unassigned
              13f613b9d7ca Grant Wells
              Votes:
              0 Vote for this issue
              Watchers:
              65 Start watching this issue

                Created:
                Updated:
                Resolved: