Hi,
I would like as part of the retrospective to get some idea on how many tickets were added to the sprint and how many tickets where removed.
The easiest way to do it (I think) is to check on which date the Sprint field was changed to include or exclude the Specific Sprint name, is there a way to extract this data in Jira?
Explanation:
1) Extract all tickets that had/have, sprint field the value X in some point in the history
2) Each ticket might have more then one line in the report.
I can suggest at least two solutions with our apps.
Easy
Using the PDF View Plugin you can export the Burndown chart and the related "event table" to PDF.
And then "sprint scope" type events display what you want to see!
See this sample PDF.
More manual, but also more flexible
See this sample XLSX.
Hi,
Thank you for the comprehensive answer.
The first option does not allow me to manipulate the data so I believe I will drop it.
For the second offer as I understand to extract history of issues I must have the better excel plugin, correct?
Also it will provide me information only for issues that was added to the sprint and I will be missing the ones that was removed, correct?
Thank you in advanced and have a great week a head,
Idith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For the second offer as I understand to extract history of issues I must have the better excel plugin, correct?
Yes.
Also it will provide me information only for issues that was added to the sprint and I will be missing the ones that was removed, correct?
No. It will support both. From the change history point of view, both "added" and "remove" are just changes in the value of the "Sprint" field. "Added to sprint X" is when the new value of "Sprint" is "X", while "removed from sprint X" is when the old value of "Sprint" is "X".
I hope this makes sense.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's true. At the moment it is for Jira server and data center editions, only.
Please vote for the cloud version here and tell you requirements, use case, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi I have the query with the sprint changes. But How can I see all the Stories at the Start of the sprint (for example at the end of the 1st day of the sprint) , so I can compare them with the "real time"?
I have like 3 cases/scenarios :
1.- Issue is created and added to the sprint before sprint starts.
2.- Issue is created once the Sprint has started
3.- Issue is created before the sprint starts , and added once the sprint starts (from backlog to active sprint)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not aware of a way of doing this using out-of-the-box Jira, apart from via the REST API.
Manually, you could look at the details below the Burndown chart and look in the Event Type column for the words Scope Change. Depending on how many issues you have in a sprint, this may not be a huge task.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you so much.
I will look into the REST API
Your second option got me closer, as I copies the data to excel (yes, simple copy paste) and then from the Jira extracted missing information such as issue type and then manipulated data. a lot of work but currently this is the only way I see to get it.
Thanks a gain, and sorry for the late response, was busy testing your suggestions :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.