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; } } }

How can I retrieve any issues that have been around in more than one sprint?

Amirhossein fathollahi madani_9iufce

My team velocity has been affected recently and has been fluctuating over the last few sprints as there are some issues that haven't been done even though they were supposed to be done in earlier sprints. Therefore I want to investigate to find issues assignees and numbers of sprints that haven't been finalized yet.

So the expected outcome would be a list of issues with sprint names and different assignees they would have been carrying those issues.

Accepted answers

Yuliia_Borivets__SaaSJet_

Hi @Amirhossein fathollahi madani

If you're comfortable with using solutions from the Marketplace, there is one I'd like to suggest from my team. Consider Issue History add-on. It shows all the updates made to the selected issue list. So you will see issues, their assignees, sprints and any other column. You can filter by project, sprint, assignee, label, etc.

It allows auditing the teamwork. Check if it will be helpful for your case.

Kind regards

Yuliia

All comments

Bill Sheboy

Hi @Amirhossein fathollahi madani

As you note your team is using Scrum, I encourage you to discuss this symptom with the team rather than single out individual people. With Scrum, the team owns meeting the goal, not one person.

If the team is currently in a sprint you could see these carry-over issues with a JQL query. Just replace myProjectName with your project.

project = myProjectName AND sprint IN closedSprints() AND sprint IN openSprints() ORDER BY Key

If you want to check this condition for just closed sprints, that is not possible with out of the box JQL. For alternatives:

There are marketplace additions to JQL which could do such a query
You could export the issues and then count the sprints using a spreadsheet
You could build an automation rule to count the sprints for closed issues. Such a rule would only work for up to 100 issues due to automation limitations.

Kind regards,
Bill

Amirhossein fathollahi madani_9iufce

Thanks for your reply @Bill SheboyI totally agree with you, however during the past 2 months that I have joined this new team as a product manager/owner, I have been communicating scrum values to my team members as a whole, but results have been worsening and commitments are not fully achieved.

I ran the mentioned query in filters but only showed me the existing issues in this sprint. would you be able to suggest to me any other query that returns open issues with their sprint history?

Bill Sheboy

Hi!

For the current sprint contents: If you add the sprint field to your query results, you may see them on the page view with advanced issue search. To do more analysis (like count of sprints) you may export the results and count in a spreadsheet with formulas.

For earlier sprints: search for issues where sprint IS NOT EMPTY, and again view on screen or export for analysis:

project = myProjectName AND sprint IS NOT EMPTY

Yuliia_Borivets__SaaSJet_

Hi @Amirhossein fathollahi madani

It allows auditing the teamwork. Check if it will be helpful for your case.

Kind regards

Yuliia

Amirhossein fathollahi madani_9iufce

@Yuliia_Borivets__SaaSJet_ Thank you so much. It helped me a lot!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud