According to Atlassian's documentation:
"An issue will only be visible in the Scrum backlog if: (...) the issue's status maps to one of the board's columns"
(from Using your Scrum backlog)
I think this is a problem.
Here is my use case:
Because of Jira's limitation, if I want to see the New issue in the backlog, I have to map the status New to one of the Scrum columns.
I don't want to do that.
Am I the only one to want to organise my projects this way and thus to have this problem?
Hi @Thomas Schlegel!
Some Scrum Masters and Product Owners separate the Product Backlogs and Sprint Backlogs during sprint planning; the product backlog contains all of the stories in the project. During sprint planning, the PO selects the stories for the next sprint and then moves them to the sprint backlog. The Scrum team then writes sub-tasks for each story where needed, and the set of stories and sub tasks becomes the sprint backlog.
I've found that this setup gives more autonomy to the Scrum team; it allows the PO to set WHAT will be included in the sprint, while the Scrum team defines HOW the stories will be developed. It can be tough to get used to, but I've seen it work.
I suggest having two boards in the project; a Kanban board with all the current Scrum board columns, plus the "New" column, and a Scrum board with just the current Scrum columns. The Kanban board becomes your product backlog, During story grooming or sprint planning you can review the "New" items in the Kanban board and move them to the "To Do" column. All the stories that are marked "To Do" will show in the Scrum board as the sprint backlog.
Does this help?
Hey @Scott Theus, yes this is more or less what I did.
One of our workflows allows undiscussed issues to be injected at different steps (concept art sprint, dev sprint, etc).
So we now have a "discussion" dashboard that lists all these new issues as @Thomas Schlegel suggested, but also a "planning" kanban board allowing us to graphically move those issues to the various initial sprint statuses.
Eh? You put a status in a column. I don't see how that is "too much bureaucracy" when the principles are explainable in a short sentence and it's a single action.
I would like to have only one board and not need to map the 'BACKLOG' status to any of the columns there.
What I have now is either create a new board and follow the suggested steps or keep seeing things going to the 'To do' column with the status 'BACKLOG', which is really sad.
Exactly, I want the 'BACKLOG' issues to be shown only on the BACKLOG. Once I move it to the sprint, it should be 'at least' with TODO status.
So I want the status 'BACKLOG' to be mapped only on the 'backlog', not any column of my board or any board, hehe.
I would like to have only To Do, In Progress and Closed columns (mapped to To Do, In Progress and Open statuses) on the Active sprints board. I don't want to see the Backlog column there which is mapped to BACKLOG status because it's always empty - when I put a ticket into a sprint I move it from BACKLOG to To Do.
But if I delete the Backlog column / unmap the BACKLOG status all tickets on the Backlog page/view are gone. I would like to use the Backlog view for prioritizing the product backlog but I don't want to see an empty column on my Active sprint view.
Hi @David Roulin,
a backlog is meant to include issues that have to be done in a sprint (and which are ready to be done within a sprint).
So, if your "new" status is something, that has to be discussed yet and it is not even clear, if issues in that state will ever be done, they should not be part of the board. If the discussion is part of a sprint, it should be included in the board.
Your backlog is the source of issues for the sprints. And therefore, every status in the board has to reflect an issue status in your sprint.
I would not include the "new" status in the board. Manage the discussion status on a dashboard instead.
What's the difference between a project backlog and a sprint backlog? A sprint backlog is, in my opinion, the part of the project backlog which is added to a sprint.
So, the backlog is the project backlog. But part of the project is, to get back to @David Roulin's question, also the discussion about new issues. And if this is not being done within a sprint (which is totally normal, I think), it should not be part of the board.
I had the problem where my Sprint was empty/done and all my issues are in the Backlog. So when I am looking at the Backlog screen there is a sprint with no issues in it and I believe it said Start Sprint still. I was in the habit of working from the Backlog in this project and when I changed one of the issues in the Backlog to Testing status, it was disappearing from the Backlog. So it was hidden and forgotten.
This thread helped me solve my problem. I went to the Board Settings and found Testing was in the uncategorized column. I created a new column for Testing and dragged it into the new column. Then, when I went back to the Backlog the Testing issues were still hidden, even after reloading the page, so I was concerned the fix did not work and there is another problem.
After some experimentation I found that if I moved issues into a Sprint, hidden issues were all exposed in the Backlog. Hope this helps others.
It seems the route cause is the category of the status which does not match the category of the column in the Active Sprint (board Configuration).
Status Deferred (yellow) is mapped to column Done (green) that stores all final statuses.
Issue type Bug in status Deferred is not visible on the Agile Board.
To create a separate column on the Agile Board e.g. Deferred in a yellow category and map a Deferred status to this column.
Issue type Bug will show up in the Backlog.
Option 2 (I personally do not recommend)
To create (use existing) separate Agile Board with filtered all issues that are in the Deferred status but not assigned to any sprint.
However, my experience with the Agile teams shows that people prefer to have everything in one board, so they may forget checking other places. It will result with not planned/ completed issues.
Option 3 (I personally do not recommend)
To assign all Deferred issues to the sprint under the current Agile Board.
However, it requires:
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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