Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90891

Changing Issues from Standard issue types to Sub-tasks, or vice-versa, causes problems in Sprints

XMLWordPrintable

      Summary

      Converting issues currently in a Sprint to sub-task whose parent is in a different Sprint or no Sprint at all, causes a bug in which the sub-task issue will still display as if it belongs to the old Sprint (not the parent one).

      Environment

      Cloud

      Steps to Reproduce

      Scenario 1

      1. Create a standard issue in a Sprint
      2. Convert this issue to a sub-task whose parent is in a different Sprint or have no sprint at all.

      Scenario 2

      1. Create a sub-task issue in a Sprint
      2. Convert this sub-task to a standard task and put in a different Sprint from the parent.

      Expected Results

      The issue should be displayed under the parent's sprint, or in the correct Sprint, depending the case.

      Actual Results

      The issue is displayed in the old incorrect Sprint, not respecting the current parent sprint.

      Notes

      First report: Oct-11-2017
      In some cases clicking on the View on Board link on affected issues will give the user "Page unavailable".

      Workaround

      None for now.

        1. image-2017-10-12-16-30-44-827.png
          60 kB
          Martin Véronneau
        2. Screen Shot 2022-06-17 at 11.12.48.png
          23 kB
          Leonardo De Almeida
        3. Screen Shot 2022-06-17 at 11.09.23.png
          40 kB
          Leonardo De Almeida
        4. Screen Shot 2022-06-17 at 11.06.22.png
          261 kB
          Leonardo De Almeida
        5. Screen Shot 2022-06-17 at 11.34.58.png
          237 kB
          Leonardo De Almeida

              39c9abcf55e0 Rafael R
              aborzzatto Andre Borzzatto (Inactive)
              Votes:
              25 Vote for this issue
              Watchers:
              29 Start watching this issue

                Created:
                Updated:
                Resolved: