Issue burndown diagram for subtasks - when Issues are part of multiple sprints

Dear community,

Our problem is that when an issue is part of multiple sprints, finishing the story or task took multiple sprints, eazyBI only shows sprint related data of the last involved sprint (when was the issue added to the sprint or commited to the sprint). for example, if the story was created in sprint A and was in progress in sprint B and finally finished in sprint C, only the sprint C related data can be used, the date when the story was added to sprint A is not available. The “Sprint issues added” and “Sprint issues commited” agile measures are only contain the last sprint data for a specific issue.
Is this is a feature or a bug? In case this is a feature, is there any workaround to get the “Sprint issues added” or “Sprint issues commited” data for every sprint that contained the given Issue?

thanks in advance,

Hi @csibug

It is very likely that you faced the limits of Jira in your report requirement.

The main problem is the lack of Sprint change history for issue sub-tasks in JIRA, as information from the issue change log is used to calculate Sprint scope measures.
Sub-task sprint change history is not saved in its changelog, and sub-tasks are always counted by their parent actual (last) sprint (except for the measure “Hours spent” which is specifically processes).

We have opened the issue in Atlassian support, but it was closed as duplicated. Original issue by Structure is not resolved yet.

At the moment, only rough workarounds are possible, but they could be very slow and complicated (it requires many iterations in MDX).

Ilze /

Thank you for your answer!