Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Can the order ranking of tickets in the Scrum and Kanban backlogs be synced?


My team is switching to using Scrum from Kanban for a project. I noticed upon creating a Scrum board that the backlog is sorted entirely by ticket # / issue keys. The board filters are the same. I was wondering if there was a way to have these be aligned without having to re-sort these all in Scrum as there are a lot of tickets in our backlog. 

I was unable to find a current solution based on searching various posts and tried searching looking through the various board options settings. I understand that the Kanban and Scrum boards are meant to be distinct due to different work system conventions (sprints vs continuous flow) and that's likely why these aren't aligned to begin with. Appreciate your help. 

1 answer

1 accepted

4 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 05, 2021

The simple answer is to use the same "order by" clause in the filters for the boards. 

In fact, you could just use the same saved filter for both boards, so that if you do have a reason to change it, you don't need to do it twice to make them match!

When you look at the board settings, you won't find that the issues on the new board are sorted by issue key, they're actually sorted by rank.  They look like they're sorted by key because each new issue is created with a lower rank than the existing issues.

Hey Nic, thanks for the response. I realized my issue and what you pointed out. They did have the same filter and ranking. My mistake was that I closed out some old sprints that a past admin/PM had set up and these polluted the ranking since this placed all of those legacy tickets at the top of the Scrum Backlog. After reviewing the list I did see the later tickets were sorted in the same order after that. Thanks!

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events