We had a challenge today after we needed to move a issue that belonged to a sprint into another Jira project (a project without a scrum board). We then found issue was no longer visible on the agile board (makes sense in hindsight, since the board's filter wasn't looking in the project the issue was moved to), but the issue itself (per the issue's details screen) was still attached to the sprint.
We looked into ways to remove the issue from the sprint, and we found a solution to temporarily change our "edit issue" screen configuration (per this post - https://confluence.atlassian.com/display/AGILE/How+do+I+remove+all+Sprint+related+info+from+an+issue)
I'm a little reluctant to make this "edit screen" change permanently (I could foresee problems with allowing the users to edit the sprint ID directly). I guess the other (and perhaps easier) solution would have been to move the issue back to the original project, remove it from the sprint, then move back to the destination project.
Any observations / better ideas?
The other workaround we thought of (and the one we used) was to change / resave the filter driving the board temporarily (to something like "project = ABC OR key = XYZ-123", which allowed us to see the moved issue on the board and take it out of the sprint (then changed the filter back to its original query).
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs