HI
We are using jira/rest/agile/latest/board/<board ID>/sprint/<sprint ID>/issue to extract issues of completed sprint. This API is run 2 days after sprint closure and by then the new sprint has started. The extracted issues are stored in a DB and using this data we do some calculations, for e.g. total committed SPs and completed SPs. It is possible that a issue which was not closed in previous closed sprint changes story points or any other field in the new active sprint, which is perfectly fine. Teams can change SP when new sprint starts. What we have observed is that the DB stores the latest SP value for the completed sprint, for e.g. a 5 point in sp1 was changed to 3 point is sp2. The DB stores 3 points for SP1 as well as SP2. where as the jira report shows 5 for sp1 and 3 for sp2. this makes our calculations unreliable. Is there anyway to solve this problem? The issue ID is same but sprint IDs are different. I want to see 2 different story points in DB for 2 different sprint IDs for the same issue as is visible in the jira sprint report.
Thanks,
Pooja
Hi, @Pooja Wandile. There's an online community specifically for Atlassian developers. You may want to try posting this question there for a faster (hopefully) response.
👉 Atlassian Developer Community
Good luck,
-dave
Hi, @Pooja Wandile
That's the problem with the JQL search and working via API; both approaches offer only the final state of a particular issue. That's why the majority of reporting apps can't be utilized in dynamic environments where estimation and other fields change frequently.
That's why we created two apps:
Charts in both of apps show you the historical data, so you even can see the Initial Commitment at the start of the sprint:
If you need to pull this data into another tool (Bi, Google Sheets, Excel, etc) you can use the Live Data link feature:
Is it something you are looking for?
Hope you find my answer helpful,
Olexiy
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.