Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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

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
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

314 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you