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

How can I view status in backlog without having to map all status in a board

For my project I have 3 boards a kanban board each for analysis and testing and a scrum board for development. I have status's that are mapped to the analysis and testing boards and not mapped to the development board. This means however that when looking at the backlog view the tickets that do not have status's mapped to the development board do not show up in the backlog view. Any ideas how to make it so I can see all tickets in the backlog without having them mapped to the development board.




6 answers

Nic Brough: "You can't.  You're effectively asking to see issues you have chosen not to see.  It's one or the other.

If you want to see an issue on the board, it needs to be selected by the board to be visible - the board filter needs to select it and it needs to be told in what column to appear."

No. I'll go out on a short limb, and say it. You are incorrect. You're trying to "fit" Scrum to the limitations of Jira. This is NOT "how a Backlog" in Scrum "works". 

Any WORK, is the backlog (things that are or might become "Product").  Whether

  1. Done or
  2.  in a Sprint,
  3.  or NOT as yet in a Sprint.

A board, to visualize the NOT the backlog.

What the OP is trying to compartmentalize is:

As a Customer

I want to see

Jira Backlog Screen -> Display (2) and (3)

Jira Active Sprint Screen -> Display (2) and (1)

So I can...DO MY WORK.


This IS how Scrum differentiates Backlog (the work) from Board (a particular visualization I've decided might be useful for display the flow of the work). Not because I'm both a Scrum and Kanban trainer (because I am), and not because I say so, because that's what the Scrum Guide says (and speaking as the original translator of the Guide into Spanish, I think I'm pretty familiar with what it says).


Jira has this woefully broken. I hope others find this, and upvote this to the sky, because the day Atlassian FIXES this, it will actually have accomplished something very useful to A LOT of people.

The way you have written this suggests that you have not even looked at a Scrum board in Jira software.

If you had, you would see that a Scrum board has two views you switch between

  • A backlog, which lists all issues selected by the board filter except those that are complete.  This includes issues allocated to sprints - the sprints are boxed out at the top of the list.  If used as intended by Atlassian (ordered by rank) you can re-order the backlog and move things in an out of sprints
  • A board or card view, which shows the current active sprint and allows the developers to move things around.

So Jira already does almost everything you describe, exactly as you say in your "As a customer I want to see" bit.  Your essay barely has any reference to the original poster's question or my response.

You have also got the definition of backlog wrong.  You say "Any WORK, is the backlog (things that are or might become "Product").".  This is broadly correct.  But you then say "it includes done items".  This is absolutely wrong as "Backlog is simply a list of all things that needs to be done within the project." - in other words, a backlog does not contain done issues, because they do not need to be done, because they already are.

"A backlog, which lists all issues selected by the board filter except those that are complete.  This includes issues allocated to sprints - the sprints are boxed out at the top of the list."

-- this used to be true. Now, even if I have the backlog status included in the filter, if I do not have it mapped to a board column, it will not show on the backlog view. Even if items in the backlog status will never show on the board (because I will never assign them to the active sprint), I still have to actually /map/ it to a board column in order for it to be visible under the created sprints, which seems bizarre to me. But as I've said, I am pretty sure it used to work exactly as you describe, and paid attention to the filter only rather than the mapping. 

Like # people like this

Just having this issue myself, I'm surprised at the divisiveness in this thread as it seems straight forward to me, and agree with the original poster; the backlog should be based purely on the filter for the board, not on whether statuses are shown on the board columns or not.

I have multiple board views for different roles, so devs for example don't need to worry about all the steps done before a ticket is ready for development (ie design/discovery sprints) or statuses for the steps the testing team need to do once development is complete.

I'd still want to see all backlog tickets irrespective of which board I'm viewing. I've had to create one board to rule them all which incorporates all statuses, JUST so I can see the full backlog, then I have to switch to my PO board or whatever to see the statuses and columns I want to see on the actual sprint. Sprints and backlogs should be separate, and the backlog should show all backlog tickets irrespective of the statuses I have in my columns on the sprint board.

Yes, that's right, a board shows you everything that a filter selects for.

The thing that is a problem here is that you can leave status out of a board mapping.  It's not wrong in itself, a lot of us have uses for boards that ignore issues in certain status.

What you are not understanding is that choosing to ignore a status in a board means, well, you don't see it on the board.  You have chosen to ignore that status.

Which is it?  Do you want to see all the issues irrespective of status, or do you want to ignore some.  The backlog and the board are different views of the same list.  It's not right to have them give you different lists.

Hi Amy,

Create a status called backlog and configure this status to not be in the board columns.

Hi Cristian,


I have this status already but if it is un-mapped in a column then tickets in this status do not show in the backlog view.



There is a difference between unmapped and used as backlog.

Check the image belowCaptura.PNG

Hi it's a scrum board rather than a kanban board, can I still do this? It doesn't show up when I open the configure kanban column?





This is how scrum works. Scrum board doesn't have a backlog in a sprint because in a sprint you are working in those issues. The backlog in scrum is the list of tasks outside a sprint and, when a task is in a screen, it is not in the backlog anymore.

Anyway, you can see the issues in the "backlog" menu but above the "backlog" and it is called sprint.


I think I'm not explaining myself clearly so hopefully the below example will make sense.


I have a staus called BA To Do, this status is currently only mapped to the analysis board. If there is no sprint tagged in a ticket with this status and I go onto the backlog view in jira this ticket does not show in the backlog. If I map this status to a column within the development board it does show in the backlog. I would like to know how I can have this status un-mapped to a column but still show tickets in this status in the backlog view.




You can't.  You're effectively asking to see issues you have chosen not to see.  It's one or the other.

If you want to see an issue on the board, it needs to be selected by the board to be visible - the board filter needs to select it and it needs to be told in what column to appear.

This answer doesn't make sense to me... 


The backlog should display all issues in all statuses. 

The active sprint should display all issues sorted into the columns I've created and the statuses I've mapped to each status. 

In my workflow, I have a status called "Awaiting Review". This is the first step in the workflow before it's transitioned to "Ready for Development". I don't need the issues in the "Awaiting Review" status to be visible in the Active Sprint board because those issues are not ready for the developer to work on, but I do need them present in the backlog. 

How am I supposed to groom my backlog if there are some statuses that don't appear here...?


You are not asking for a backlog, but for a report. A backlog is all the work that you haven't even started. When you have started to work on an issue, then it is in your board and it dissapears when the work is done.

Make a Dashboard or a filter which displays the issues as you need.

I am very new to scrum. 


Still this is a feature I need. It's just weird it doesn't work. I don't want a column for backlog in my Sprint. It distracts from working. 

I want to see only the Sprint stuff in the columns not the backlog. But if I don't map it to a column it's not there. That's really weird. 


Should be a easy fix 

That's the point of the discussion - it does work.  Some people want a backlog column, others do not.   You can (now) choose.  I prefer backlog on one view, and my current sprint on the board view.  But that's just me.

How is it possible?

In kanban yes but in scrum not. 

I have a scrum board that pulls issues from a lot of projects. If I don't map the backlog status to a column it won't show in the backlog of the board. 

If you do not have a status on the board, then it is not part of the board.

The backlog is part of the board.

So, yes, if you don't map a status, then issues in that status CAN NOT appear as part of the board, and that includes the backlog.

But I want that feature. Just for the backlog. I don't want to know how it is in jira. I want it for my Individual scrum board. Jira writes everywhere they don't tell you how you should use scrum. So why is that not a feasible option?

It's not about "doing scrum", it's about what the board is showing you.  A board is a view, not a container.

If you do not map a status, then that status is not part of the board.

It's not a "feature" to do this, it's just incorrect.

Hey Nic,

I understand your point. I understand that in JIRA the board is a view and not a container. That's the infrastructure behind JIRA.

I as a customer would like to have an extra feature. Let's not call it the board then. I want to be able to have the backlog where I can plan the sprints. I want this apart from the board. I want the board with the colums NOT to show the backlog. It just creates stress in the peoples heads that want to just do their stuff. They get stressed. Its mental not IT.

If it doesnt work in JIRA okay fine. If they cant do it fine. But the wish to have it is still very reasonable and okay. 

You can't do this.  The backlog and sprints are part of the board.  They're the same data.  Your scheme would break because data is missing from view.

I am new to Jira and ran into this same “issue” today. In my project, new issues are created with status=“Backlog”. My scrum board has “To do”, “In progress” and “Done” columns mapped to the statuses of the same names. Since status=“Backlog” issues are not mapped to my scrum board columns, those issues do not show up in my scrum board nor my scrum backlog. 

I propose the scrum Backlog page/list should show all issues, regardless of status, that are not currently in a sprint and not completed(?). I initially expected to see my status=“Backlog” issues included. Assuming they are displayed, the question becomes how should they then be presented on my scrum board? I suggest that the an unmapped issue status should be changed to the status mapped in the left-most column on the scrum sprint board. Isn’t that essentially what I would be doing by specifically moving a Backlog issue of any status from the scrum Backlog to a sprint?


if there is already a way to do this, please let me know. 

The point of a backlog is listing, ranking and selecting the issues are supposed to be able to go across the board.  If an issue can't go across the board because it's not on it, there's no point having it in the backlog.

I understand that is how it currently works in Jira. I believe the point myself and others are making is that this isn’t what many expect. Do users consider items listed under “Backlog” as ready to go across the board? Maybe there should be a board configuration option to “show unmapped statuses in backlog?”. 

To expand upon that idea, the user would go into the board configuration and place select specific unmapped statuses into a “include unmapped status in Backlog” box. This way the user can choose which statuses are included/excluded in the Backloglist. Again, It should then be made clear that including any of these unmapped status issues into a sprint would automatically update the status of the issue. 

My proposed solutions are simply to satisfy the expectations of more users to make for a better UX and help make the product more flexible. 

Yeah i think it would be easy. But as you can see nic just repeats it over on over again. It's just not how they want it to be. Sad to hear the same answer over and over. Very dissatisfied with this community Forum the way we are treated. It's how it is. I won't post anymore here. 

The reason I give a similar answer repeatedly is because people are not understanding what I've written before and I'm trying to explain it differently.

Please don't abandon the community just because you don't like or understand a particular answer.


I encountered the same issue today and found this thread. Though the thread did not give any solution, but it confirmed that it is an existing behaviour (i.e.) unless you map the status on the board, you cannot see those issues on Backlog.

I used a work around to address this issue. Created a new filter on the Active Sprints board  using JQL to exclude all the issues with status'  that I don't want to see on "Active Sprints" board. But mapped those status on the Broad settings to one of the existing column (e.g. Sprint To-Do). That way I can see those issues in "Backlog" board but at the same time it is not visible on "Active Sprints" if filter applied.  

Suggest an answer

Log in or Sign up to answer

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