Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

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

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!

Akshay,

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?

https://confluence.atlassian.com/display/GH/Configuring+Columns

Hi,

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?

Hi,

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

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Agile

Join us LIVE: Atlassian & Experts Talk Research & Insights @ Scale

Hello all! What have you learned from your customers lately? Our live-streamed series continues by exploring CX, UX, and the power of research & insights at scale with Leisa Reichelt, Head of R...

249 views 3 6
Read article

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