nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Filter bug count to created during current Sprint

Bud Herz_4dzuwt

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.

Accepted answers

Kevin Johnson_3sxc8m

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.

-Kevin.

All comments

Kevin Johnson_3sxc8m

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.

-Kevin.

Bud Herz_4dzuwt

Awesome it works! Thanks so much!

Bill Sheboy

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

Bud Herz_4dzuwt

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

issue

cloud

jira-software

jira-software-cloud

agile

filter

metric