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

How do you handle issues that are blocked for the current sprint?

Our team has just recently started using Greenhopper. We just started our first sprint. However, one of the issues, creating a wallboard for the sprint, is blocked by https://jira.atlassian.com/browse/GHS-5345. From a greenhopper perspective, how should this issue be handled, since I obviously cannot get this done in the current sprint?

1 answer

1 accepted

0 votes
Answer accepted

You know from reading the comments on the linked Atlassian JIRA that you don't know when this will be worked on.

Your issue will have to be moved back in to your backlog. If you are not prepared to wait for Atlassian then you will have to come up with another solution.

Yes, I realize this. However, should this be done now, since we know it's blocked, or at the sprint review? What are the advantages/disadvantages of each from a visibility, tracking and reporting standpoint? Does it even matter when it occurs?

It does not matter when it occurs. I suggest you can organise the backlog JIRA now if you have time and it can be discussed at the review. This story/task will not be part of the release notes for the sprint and so will not be reported.

As regards tracking, it's all about your backlog, everything is visible in there. Towards the top of the backlog should be in priority order and groomed.

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...

270 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