Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

cant see issues in backlog when creating scrum

We have greenhopper 6 and jira 5.2 and previously we have used kanban boards - we now want to set up and use a new scrum board but even though we are using the simplified workflows and the filters are definitely correct no created issues ever appear in the backlog - if created from within the scrum we get a message saying issue created but not visible!

We would like all issue types to display so we can assign them to sprints if possible but if not we would at least like to see the stories, at the moment nothing is ever usable

3 answers

Akshay Pindoria - Did you finally resolve the issue as we are facing the ssamething here?

0 votes


Two things which decides whether the issue is shown, one is the filter used for the board, and the next is your column to status mapping. Can you confirm that both are okay?


Thanks for the answer - we have set the simplified workflow and we then went to configure and assigned the statuses to the columns - we are certain that the filter and the status mapping are correct.

We're a bit confused tbh

Ok, couple of questions:

  1. Hope that you have not selected any quick filter that is hiding the issues, as the screen shot says that there are 32 issues for the filter
  2. Simplified workflow automatically maps statues to columns, wasn't the statuses already mapped after converting to simplified workflow?


when we create the scrum board the statuses are unmapped - we have to manually add them to the columns?

Newly created issues are put into the Scrum Product Backlog rather than changing the scope of the current Sprint.

In GreenHopper terms, this means your new issues will be visible in Plan Mode but not Work Mode.

That is the problem - they AREN'T visible in Plan mode!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events