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

Scrum Project Backlog Contains Issues with Status with Status Other Than Backlog

Why in the world would you configure the scrum style backlogs to include issues of all status's. The backlog is the BACKLOG and should not have items that are in progress or complete included. This makes backlog grooming and prioritization unnecessarily complex and arduous. I get that the strike though on the issue number is used to indicate the issue is done, but issues that are complete or in progress should not be cluttering the backlog. Applying a filter does not work, because filters apply to all views not just the display in the backlog.

Also. a more minor issue but still a nuisance, moving an issue that has a status of backlog from the backlog to a sprint as part of planning and refinement should automatically transition the issue to ready.

Is anyone else having these issues? And if so, have you found a simple solution? So far a script runner is the only solution we could find and that may or may not work. However, these are very basic Agile scrum concepts that should not require add-ons to enable.

2 comments

Hi @Brooke Brown ,

 

Did you configure the columns of your board? The article below might help you with this.

https://confluence.atlassian.com/jirasoftwarecloud/configuring-columns-764477997.html

 

Thanks,

Sanjana

Thanks, yes I did. It is not the board that is the problem. It is the backlog. My backlog shows 559 issues of which only 179 are true backlog status issues that need to be groomed and planned into a sprint. I need the backlog to only show true backlog issues. My current workaround is to send all of the tickets that are not actually in a backlog state to the bottom of the backlog, but its just messy and creates unnecessary noise.

Hi @Brooke Brown  

Not sure what else could be the problem apart from the column mapping. I found this article, it might help you. Make sure to put the "Done" column in the last. 

https://confluence.atlassian.com/jirakb/closed-or-resolved-issues-are-appearing-in-the-scrum-board-backlog-779159078.html

Thanks,

Sanjana

Comment

Log in or Sign up to comment
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

66 views 0 3
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