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

Your Points Tracker
  • 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
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?
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

Filter bug count to created during current Sprint

We have a filter to graph the bugs in the current Sprint. 

project = FS AND issuetype in (Bug) AND Sprint in openSprints() ORDER BY created ASC


This is includes older bugs we pull into the Sprint and bugs created during the Sprint. Older bugs are viewed as "Planned Work", but I am trying to illustrate the increased workload coming from new bugs. I would like to constrain it to bugs created during the current Sprint. While we don't point them, they do add to the overall Sprint workload. 

1 answer

1 accepted

0 votes
Answer accepted

Hi @Bud Herz ,

project = FS AND issuetype in (Bug) AND Sprint in openSprints() and Sprint not in closedSprints()

This should get only the bugs added in the current active sprint, not from the old sprint.

Hope this helps.


Awesome it works! Thanks so much!

Hi @Bud Herz 

There is an edge case this query will not find:

  • defects (bugs) discovered, and logged into the backlog
  • which were not worked on in a prior sprint, and
  • which were selected for work *during* sprint planning

Those defects were not added after sprint start, and so are not scope change.

When you need to specifically see defects added to the scope of the sprint *after* it started, please consider either:

  • using the sprint burnup chart report to see things added to the sprint, or
  • using an automation rule to detect this condition, and mark the issues as such

Best regards,


@Bill Sheboy those are great points, but in our workflow any new bug is handled during the current sprint (To Do, Doing, Done).

The bugs won't (potentially) move to the Backlog until the end of the sprint. That would move them off the list I'm trying to create (bugs created in current sprint).

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
Site Admin

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