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

Why I can't see bugs in my sprint?

Hi guys,

I have a problem in displaying the issues (bugs) in the current sprint

The steps i've done are the following:

From the Board view --> Board Settings --> General

Here I've set the query

project = FZ AND issuetype in (Story, Task, Epic, Bug) and sprint in openSprints() ORDER BY Rank ASC

Every time I need a bug to get fix in the current sprint, I compile the dedicated field (Sprint) of the ticket.

Why I can't see these bugs in my actual sprint?

Thank you for your time and your help

 

1 answer

1 accepted

2 votes
Answer accepted

@Elisa Cartolano 

The reason why they do not show up in the current sprint is because a Sprint is a committed piece of activity agreed at the start of each sprint period. You can include those bugs that already exist at the start of a Sprint but any new ones will automatically go in to the backlog for a future sprint. 

Whilst you can just bring new bugs in to the current sprint, this would be altering the scope and would mean the commitment to deliver the agreed scope would no longer hold true. 

If you want to continuously work on the highest priority item (bugs, stories, tasks) then it is possible that a Kanban approach rather than Scrum would suit your team better?

 

I would suggest that if you continue with the Scrum approach you should consider removing an item of similar complexity (that has not yet been started) every time you add a bug in to the current sprint. This will allow you to retain a proximity to that Sprint Commitment that was made by the team at the start of the sprint. 

 

Phill 

Thank you Phill!

Yes, I know this approach is more Kanban, but was an exception for project needs, just for one sprint :D

Anyway, I can't find those bugs even in the backlog, but now I understand why they don't automatically show up in the current sprint.

Thanks for your precious help!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Jira issue check and more advanced commit verifications for Bitbucket DC

Pre-receive hooks that verify the Git commit message, the modified files, and implement similar code change controls used to be requirements of large enterprises working in regulated industries only....

31 views 0 2
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