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

Convert Subtask to Issue messed up Sprint

XMLWordPrintable

      I converted an estimated subtask of the active Sprint to a story. It landed in the backlog with no warning about Sprint scope changing. Then when I moved it back into the open Sprint I got the warning and my remaining hours line went up.

      At worse, this should be net 0 hours change with a blip but I've ended up with the extra time in my Sprint. Presumably the extra hours are duplicated somewhere but I can't find them so far.

      Is this a bug, or did I do something wrong perhaps? Any suggestions to fix my sprint?

      I'm using JIRA v6.1.7 and JIRA Agile v6.3.7

        1. blip.PNG
          blip.PNG
          0.3 kB

          Form Name

            [JSWSERVER-12258] Convert Subtask to Issue messed up Sprint

            Kiran (Inactive) added a comment -

            Hi Lain,

            You are describing 2 problem here.

            1. The sub-task moved out of the sprint into the backlog, when converted to a story. Issue raised https://jira.atlassian.com/browse/GHS-12335
            2. The burn-down chart did not record drop in estimate when the sub-task when out of the sprint. The current behaviour is that JIRA Agile does not add up the estimate on the sub-tasks to the stories. Hence if we remove or add sub-tasks to the story, there is no change in the burndown report or sprint scope. There is a feature request for this https://jira.atlassian.com/browse/GHS-9167

            Kiran (Inactive) added a comment - Hi Lain, You are describing 2 problem here. 1. The sub-task moved out of the sprint into the backlog, when converted to a story. Issue raised https://jira.atlassian.com/browse/GHS-12335 2. The burn-down chart did not record drop in estimate when the sub-task when out of the sprint. The current behaviour is that JIRA Agile does not add up the estimate on the sub-tasks to the stories. Hence if we remove or add sub-tasks to the story, there is no change in the burndown report or sprint scope. There is a feature request for this https://jira.atlassian.com/browse/GHS-9167

            Iain added a comment -

            In what looks like a related problem, my co-worker deleted a story from the active sprint and now even though the story is gone, the remaining hours line stayed at the same value.
            Presumably it would have been better to move it out of scope first or set the remaining hours to 0 or something.

            Iain added a comment - In what looks like a related problem, my co-worker deleted a story from the active sprint and now even though the story is gone, the remaining hours line stayed at the same value. Presumably it would have been better to move it out of scope first or set the remaining hours to 0 or something.

              kshekhar Kiran (Inactive)
              516632c00a5a Iain
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: