Splitting Issues on active sprints problem - can't send issues to backlog

XMLWordPrintable

    • 2
    • Severity 3 - Minor
    • 0

      Issue Summary

      On a Scrum board backlog (company or team-managed project), when an issue that is on an active sprint is split using the "Split Issue" option, there will be an option to choose whether the issue that is being split (original issue) or the new one that will be created should be sent; It's possible to choose to send them to Backlog, to the active sprint, or to any other planned sprints:

      The option to choose where to send issues works correctly for the newly created issue and, in case we try to send the original issue to some other planned planned sprint it also works. However, It does not work If we try to send the original issue to Backlog. In the screenshot above, I split CMST-1, creating CMST-2, ** and tried to send both to the backlog. In the screenshot below we can see that CMST-1 did not go to the backlog, as expected. It's still on the active Sprint:

      Steps to Reproduce

      1. Create a new project (cm or tm) and create a new sprint
      2. Create a new Issue, put it on the sprint, and start the sprint
      3. Try splitting the issue, and send the original one to the backlog

      Expected Results

      When splitting issues on active sprints, If we choose to send the original issue to the backlog, it should go there

      Actual Results

      When splitting issues on active sprints, If we choose to send the original issue to the backlog, it stays on the active sprint

      Workaround

      The only workaround is to manually move the original issue to backlog

        1. image-2023-11-09-09-48-39-824.png
          134 kB
          Guilherme Lima
        2. image-2023-11-09-09-53-47-686.png
          87 kB
          Guilherme Lima

              Assignee:
              Unassigned
              Reporter:
              Guilherme Lima (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: