When I export data from Jira, there are sometimes several "sprint" fields. I assume this to be a ticket that either moved from sprint to sprint or was planned for several sprints.
My question is:
How can I only export the sprint in which a ticket was actually worked on not for what is was planned for?
If i have 3 sprints:
Sprint 3 - Active Sprint
Sprint 2 - Closed Sprint
Sprint 1 - Closed Sprint
I have a ticket that was planned for Sprint 1, worked on in Sprint 2, and it rolled over and completed in Sprint 3 because it was under estimated for story points and acceptance criteria was not met.
When I export from Jira, all 3 sprints show up, but I have no idea how to see where the ticket was actually worked on. By the example, the result should be Sprint 2 and Sprint 3.
Does anyone know any tricks to pull this date out?
Thanks in advance
Thank you for reaching out.
Indeed, the Sprint field will always return all the Sprints that your tickets belonged to until its resolution.
By default, there is no way to differentiate/identify what actions were performed in the ticket during each Sprint, however, you could use a text custom field to add this information. These would be the steps:
1 - Navigate to JIRA Settings > Issues > Custom fields and create a new text custom field to collect your Sprint history.
2 - Add the field as required to your issues, informing the team responsible for the ticket to always update it with the work performed in that Sprint.
Doing it, you will be able to know by this field where the ticket was actually worked on when exporting data.
Let me know if this information helps.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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