Issues taking more than one sprint - reports

[Scott Thurston]

We would like to pull a report or listing of issues (not sub-tasks) that an individual was assigned that took more than one sprint to complete. Is there a way to query for issues that were in more than one sprint?

[Bill Sheboy · Accepted solution]

Hi @Scott Thurston 

To help the community provide ideas, what problem are you trying to solve?

You describe your team is using JIRA sprints, and so is using a Scrum board.  When a Scrum team selects work to complete in a sprint, the team is accountable for the completion of the work/meeting the goal, not one individual.  The team can discuss as a group what happened when work does not finish as planned to decide how to improve.

If this is not a Scrum team (and they are using a Scrum board for another reason) you could make a JQL filter in Issues and Filters to look for items with a non-empty sprint and assignee, include those fields in the results, and observe issues with more than one value in the sprint field.  This will not indicate if the assignee has changed over time and so may give you false-positive results.

Thanks, and best regards,

Bill

[Scott Thurston]

Bill, thanks for your reply.  Good points and a useful answer.

[Guy LaRochelle]

I don't think the answer really answers the original question however.

Is it possible at all to report on tickets that have more than one sprint assigned ?

You can definitely question the reason behind, but still, this is not an answer to the question.

Thanks

[Bill Sheboy]

Hi @Guy LaRochelle -- Welcome to the Atlassian Community.

Please take a look at the third paragraph of my response for an answer: JQL can find issues which have a non-empty sprint value and which were assigned, but cannot easily determine when they were assigned to the person relative to the sprint(s)...or even the number of assigned sprints.

JQL is not a SQL, and so cannot perform some of the needed actions.  To do those you would need one of these work-arounds:

• a marketplace addon for JQL/reporting,
• to extract the issue history with the REST API for analysis in another tool, or
• to create an automation rule to periodically check for this condition.  (Automation could count the number of sprint values found in an issue.)

Kind regards,
Bill

[Yuliia_Borivets__SaaSJet_]

Hi @Guy LaRochelle 

Plusing to Bill's answer, here is the post that might be helpful with REST API or add-ons:

How to export issue history from Jira?