You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
This question is in reference to Atlassian Documentation: Using the Backlog
Can we move a Sprint up in the backlog so it is the first one? The Sprint is started.
Dear Atlassian team,
it would be very beneficial to be able
1) to move a sprint to the top, or
2) create a sprint directly below the running one.
We use sprints to group work packages (because they can be collapsed, which is useful).
Currently, when adding a sprint, it is always added on the bottom.
Sol we have to click "Move Sprint up" 10 times or so, which is annoying.
I totally agree.
I wonder if Atlassian has this feature in their product backlog roadmap
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Wendy,
If the sprint is started it cannot be moved and it is always the first sprint in the backlog. You can reorder the future sprints(sprints which are not started) but they will always be below a started sprint. Also you can only start only the top not started sprint.
Regards,
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What about reordering multiple active sprints in the backlog? I'd really like a specific sprint (the one directly managed only from that board) to always show up first.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Janice Karin
Unfortunately it is not possible currently to do this though there is a feature request for this, it is a request for Jira Server and DC though it does also affect cloud. I would recommend voting for this issue and commenting on t=your use case in the feature request.
Hope this helps,
Danny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.