What Sprint Produced the Bug?

Ed Maschler April 10, 2024

We are creating a dashboard for management that shows the bugs that were created over the last 5 sprints, and who the bug is attributed to, and role of that person.  This has to be repeated for multiple teams.

What I am struggling to find is a way to know what sprint a bug was opened in.
I can get to when it was completed, but that sometimes is way later than when it was opened.  

IE  Sprint 5's work resulted in 5 bugs before the sprint ended. (Doesn't mean they were completed during that sprint.

2 answers

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 10, 2024

Hello @Ed Maschler 

On what would base that the bug was generated by work done during sprint X? Are you linking the newly created Bug to an issue in sprint X? Are you assigning the new Bug to sprint X when you create it, and leaving it assigned to that sprint?

An issue can span multiple sprints; if it isn't completed in the current sprint, it can get added to a future sprint. How would you know which sprint to specify as the one during which the Bug was created?

My initial thought is that you will have to actually keep track in a custom field in the Bug in which sprint the Bug originated, and that will have to be set at the time the Bug is created, either manually or through Automation.

But that will not inherently tell you if the source sprint was one of the "last 5 sprints".

Ed Maschler April 10, 2024

I was trying to draw correlation between the created date and the open sprint at that time. I understand a bug can be in multiple sprints if it is not addressed, or in no sprint at all if it gets put in to the backlog. That is why I am trying to determine which sprint it was created in.
The custom field might work.  The last 5 sprints can be put into the query since we do 2 weeks sprints 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 10, 2024

There is no native way to create a query that will look at the Created date of an issue and correlate it to Sprints that were open on that date (based on the sprint start and end dates).

Also, given that multiple sprints may be active at one time across Jira, how would you determine which of those open sprints was the one of interest?

Let me know if you have more questions around the creation of a custom field and how to fill it or construct an appropriate query based on it.

0 votes
Hannes Obweger - JXL for Jira
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
April 11, 2024

Hi @Ed Maschler

not sure if this is exactly what you are looking for, but I thought I might give it a shot anyway. Assuming (!) that your bugs are assigned to the currently-active sprint when they are created, this should be easy to model in the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of so-called smart columns that aren’t natively available, including the first sprint, along with many other sprint-related columns. Combined with JXL's advanced features such as e.g. support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting, you could model a view like e.g. this in just a couple of clicks:

first-sprint-report.gif

This is really just one of a virtually endless number of possible views and reports - you can also view and group by any other field(s), configure different sum-up styles, etc. etc.

Any questions just let me know,

Best,

Hannes

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events