I need to move a scheduled, but not active, sprint from the lowest position to the highest in the backlog.
Formerly, I would do this by simply choosing the overflow ellipses next to the "start sprint" button in the backlog, choose move up, and move that sprint up.
Now, using Jira cloud as before, that option is gone--now, two options exist only: delete sprint or start planning poker.
I am the system admin for the entire jira instance with all the permissions that belong to that role.
Suggestions are welcome!
(I've attached a screenshot of a dummy sprint with a single issue to illustrate what actions are now available for choosing the overflow ellipses)
Thanks for your thoughts Steven. Yes, there are two planned sprints (else there would be no plausible reason for the question posed, or for moving the sprint up, because by default it would already be at the top).
The purpose of leaving the screenshot was to inform the audience of the current state of the overflow button, and to illustrate that "move up" and "move down" were not present.
The purpose of the screenshot was not to establish proof of two existing planned sprints.
I understand that: However that overflow menu looks like that normally if there's only a single planned sprint.
I'm trying to help you out here without calling out all the potentials specifically:
If you simply provided a better screenshot, I'm sure I could tell you what the issue is.
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