Create multiple backlogs within one Jira Agile project

Within the plan tab, we'd like to have the following lists

  • Current sprint (already exists)
  • Backlog (already exists)
  • Unprioritized (doesn't exist, would include untriaged bugs, features, stories, etc. that aren't ready for development)

I know I can create quick filters that would show any combination of issues, but we'd prefer to easily drag issues between two backlog-type lists; this is versus opening the untriaged issue in a separate window and changing it's state to "Ready for Development" to make it show up in a filtered backlog 



4 answers

Hi Yen,

Sharing your pain. When we were using TFS, we used to have one technical debt backlog and one product backlog. The PO would prioritize the product backlog, and the team and I (SM) would prioritize the technical debt backlog. Then come the sprint planning, we will fill 20% of the capacity with technical debt items and the rest with product development. Now with Jira I can't, tks Jira.

BTW, for the people telling us we are doing it wrong, there is a special place in hell for the SCRUM police.

You're doing it wrong....  Nah, you're not in the slightest. 

Jira doesn't support this directly because it's not generally done with "multiple backlogs" (they're confusing and messy).  The "take x% technical debt in each sprint" is a great thing to do, and I wish more people did it.

The usual approach is to have a clear indicator of type - if an issue is classed as product or technical debt by using the issue type(s) or Epics or labels, you can see this in the backlog, so when you are dragging things into the sprint, and pull in what's needed.

The weaknesses there are twofold

First - prioritising single backlogs is a pain.  It's very easy to end up with the top n issues all being product or tech debt, so it's hard to re-prioritise the others up to include in the sprint. 

To help with that, I try to use quick-filters and a slight kludge.  One filter is for "product" and another for "tech debt".  You prioritise within each, ignoring the other.  The slight kludge that comes in is you have one issue that's always open, and is both product and tech debt.  When you've finished prioritising each pile, you move a handful of the top issues (ideally slightly more than the amount you'd like to get done in the next sprint) above the marker.  Then you can do sprint planning, drawing in  as much as you can from both sets of issues that are above the marker.

Second - this is the one I've not got any real fix for.  The method does not help you with sizing a lot, you have to rely on your prioritising users to get the numbers about right.

I know this doesn't seem better than "two backlogs", but it seems to work.  I stole it completely from a place that actually has five sets of inputs from users (and sadly, no tech debt, it would have been fantastic to have added that as a sixth!).

Having scribbled all of that, there are other methods.  Having three boards can do it (a main one, one for tech debt, third for product - a little clumsy because you never sprint on anything other than main which looks odd).  And another option is to implement the incoming queues as status.  A workflow would start with "open" or "new", and that would transition to either "tech debt" or "product", and your backlog is "anything in those two status", but I don't feel that really solves a lot.

Thanks Nic for your comprehensive answer. For now I have resolved my problem by creating a separate project with my tech backlog in it. Then on my product backlog I created a board based on a filter that merges both projects. If it doesn't work as well as I expect, I will try one of your options.

0 vote

Not really.  The way Agile generally works is "backlog", "in sprint and in progress", "in sprint and done", and "stuff we did in ended sprints".  Two backlogs doesn't make a lot of sense, especially as the whole point of planning is that you have a single backlog to prioritise and work on.

I suspect this is a (large) feature request that Atlassian will probably say "no" to.  But you could at least ask - raise it at

It was meant to ensure that the backlog remains clean and separate from untriaged feature requests / bugs which can grow fast and remain pretty big. I'll try raising a feature request though thanks

Can't agree with you more Yen.. while some purist may consider that only one backlog is necessary for any given project, I feel this creates limited planning  that can jeopardize development. When some projects reach a certain size, and span more than a year of development, like many of ours, multiple backlogs ARE necessary. i.e. an 'immediate' backlog to supply current and pending Sprints within a given phase of development, with another backlog for cards to be considered in the future, or past a certain stage, such as pre-deployment, and post-launch phases. Just saying based on our experiences over the past few years...

+1 Yen and Paul

I agree with YEN , we do see a need for multiple backlogs.

In ASIL Sw development , we would like to have one major Change request which flows between multiple backlogs say for example . Now the change request has cleared the design phase it should moved to development backlog 


If we have all in one place it will be more confusing .  I really see a usecase scenario to have multiple backlogs and then have different boards based on it 

You're 4 years out of date, and please see the comment further down on Boris's answer.

0 vote

May be use 2 different boards for the same project? One for triage and another for the sprint planning?

I'm aware of such an option and have implemented a few times. What we really want is to have a separate section for triage similar to how there's a separate section for each sprint. I have also tried using "Create Sprint" as a section, but sprints have to be executed in the order you create them, so that didn't work.

Hi Yen,


Did you get any solution, we too are looking for having multiple backlogs, and you are right, one backlog remains clean and other would be Unprioritized which are still evaluated.

The situation hasn't changed, because it's still the wrong way to think of it.

Suggest an answer

Log in or Join to answer
Community showcase
Bridget Sauer
Published Mar 05, 2018 in Jira Software

Jack Graves: Real Ale enthusiast with a knack for Jira Software implementation

@Jack Graves first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this followup Sh...

53,432 views 4 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot