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.
Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11665

Assign Sprints to Subtasks and Parent Reflects Current Subtask Sprint Estimation

    • 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.

      Currently, with JIRA Agile, sub-tasks can only be tied to one parent and that parent can only be assigned to one Sprint.

      The ideal situation would be to include the ability to either assign the issue to a particular Sprint (currently supported) OR allow the issue to "Inherit Sprint from Sub-Tasks" (proposed new option). Also, if the "Inherit Sprint from Sub-Tasks" option is selected, the sub-task not the parent issue is included on the Agile board. The Parent issue simply keeps record of the progress of all subtasks.

      With this option, each sub-task could be assigned a Sprint. The estimation added to the Subtask would then be rolled up to the Parent based on the Sprint the "In Progress" subtask is currently assigned. This would allow Parent issues to be tracked across more than one sprint.

            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.
            Uploaded image for project: 'Jira Software Data Center'
            1. Jira Software Data Center
            2. JSWSERVER-11665

            Assign Sprints to Subtasks and Parent Reflects Current Subtask Sprint Estimation

              • 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.

                Currently, with JIRA Agile, sub-tasks can only be tied to one parent and that parent can only be assigned to one Sprint.

                The ideal situation would be to include the ability to either assign the issue to a particular Sprint (currently supported) OR allow the issue to "Inherit Sprint from Sub-Tasks" (proposed new option). Also, if the "Inherit Sprint from Sub-Tasks" option is selected, the sub-task not the parent issue is included on the Agile board. The Parent issue simply keeps record of the progress of all subtasks.

                With this option, each sub-task could be assigned a Sprint. The estimation added to the Subtask would then be rolled up to the Parent based on the Sprint the "In Progress" subtask is currently assigned. This would allow Parent issues to be tracked across more than one sprint.

                        Unassigned Unassigned
                        4d5a39235c64 Susan Alipour
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            4d5a39235c64 Susan Alipour
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            1 Start watching this issue

                              Created:
                              Updated:
                              Resolved: