I created a new project and agile board, and have created several issues. But they do not appear in the backlog. Am I missing a step?
I can see that 15 issues exist:
But when I click "View on Board", I get this:
I'm not sure but can you check the Boards configuration. Maybe in the part "Column" you will see that no statusses have been mapped to any columns. Not sure if that also influences the Plan mode of the scrumboard but you never know.
Edit: I just did a test on our instance and it does influence what is shown on the Plan mode of the Scrumboard.
I had this same issue and maarten's first answer was the right answer. The problem was that it wasn't immediately clear to why columns might be my issue. I thought i'd elaborate on both why this happened and show how to fix it.
When I created my new project, I had copied status and a workflow from another project which wouldn't be the standard setup. This added new status in my project that aren't mapped to columns in the agile workboard. These new status appear in the unmapped status in the "columns" configuration for the project. My backlog was showing empty despite having 6 issues.
I simply modified the columns and dragged the unmapped statuses into the lane. Here i have all my statuses mapped to columns:
I think the solution does not work in the case where you do not want to a Backlog status to actually show in your swim lane/columns.
The whole point of having a backlog view is so you don't pollute your active sprint column with the stuff in backlog, and for the items to only show up in your To Do after you moved them from your backlog.
I am using the To Do as items that have been pulled into the Active Sprint from backlog, but has not been assigned for a developer.
I am having the same issue. Atlassian told me to make a backlog column on my scrum board. I don't want that column there. My issue is also complicated because we are moving from a Kanban Board to a scrum board. On the Kanban board we have a backlog column, on the scrum board, we want to use the backlog that is inherent with a scrum board. Very frustrated.
@Ingrid Maehl, I’m a bit lost on this thread likely because it seems to have veered a bit. Can you state your precise issue? This thread in fact is a bit dated so suggest we take a fresh look at your specific issue.
CertInly a scrum board will have a Backlog View that is independent of the active sprint view. I don’t understand the need to display backlog column in active sprint.
Hey @Jack Brickey and @Maarten Cautreels, I created a new thread as you suggested, because I agree with @Don Lam2, @Ingrid Maehl and @Sarah Nosratlu in that Jira seems to force us to display backlog issues in sprints:
It's possible that the filter which is used for your board filters out those issues. Can you show us a copy of the Board's filter?
On the board click on the Board button, top right corner and choose for the option to Configure. By default it shows the General tab. If not, click General in the menu on the left. This will show a page that includes your filter. Please copy this in a comment here on Atlassian Answers.
In case anyone stumbles on this and nothing above helps, I thought i'd post my own solution:
People should be aware of this small point from Jira's documentation:
"Make sure your board has multiple columns populated, JIRA Software will consider the last column that's filled in as the end column."
Essentially, you need atleast two columns on your board. In our use case, we were trying to create an external board for a vendor to use, and deleted all but one column (since they would't need to care about transitioning things). Everything was properly mapped, but nothing showed up, and the column was marked as "to do" in grey (not green). However, as expected (when you think about it), one column = last column, and in Jira last column = done/removed from backlog. Added a second column with my status in the first and bingo – instant backlog.
It's not intuitive at first that one column marked as "To Do" would still function as last column marked "Done." It's super simple, but very easy to miss if you're not combing over the resolution docs with a fine-toothed comb.
Something like this just happened to me, and it turned out to be an issue which was moved from another project, and which landed in an unexpected status which wasn't mapped to the board. Not sure how the issue landed in this unexpected status - perhaps it was as a result of the move ? Once we noticed that, it was straightforward to transition it to a mapped status, and it now appears on the board as expected.
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
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!
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