Im trying to build up a Dashboard right now and got a fundamental problem with the Subtasks.
Right now, if i check the “resolved Storypoints” over Time (Days/Months) i get the correct Answer.
November 39, December 74 etc.
However, if i try the same over Sprints, it tells me, that the first 6 Sprints have no resolved Storypoints. Which is not correct.
As far as i know, the Subtasks inherit the Sprint from their Storys, which explains my problem, since there were no resolved Storys in the first 6 Sprints.
How can i bypass this problem to show the correct amount of resolved Storypoints each Sprint?
Im new to EazyBi and BI in generel, so i welcome any help.
The measure Story Points resolved displays the current story point value for the issues. However, those are linked to the issue current sprint.
If you want to display the date from the Sprint perspective - you should look for the Sprint scope measures - Jira Software custom fields.
The measure ‘Sprint Story Points completed’ will attribute the story points to the Sprint when the issues were moved to the Done category. This might work better for your report.
Regards,
Oskars / support@eazyBI.com
Hi Oskars! is there something I could do to sum the story points of Sub tasks in the Sprint they where closed, besides the status of parent? Whats happening to me is that the parent falling to the next sprint is taking with it the points of the subtasks closed with it to the next and only counting them when the parent is finally closed. Thanks!
Since sub-tasks themselves are not directly related to the Sprint - it is not possible to track their closure related to the Sprint. Their story point closure is tracked according to the development of the parent issue.
My best suggestion would be to give those sub-tasks all the honors they deserve and promote them to rightful issues if they deserve to be tracked as such. You might then need a wider hierarchy to display the issue dependencies and relations.
Thanks Oskars for your answer. Too bad it can’t be done. From what I’ve read here and on other forums, it seems many of us share the same need/scenario. However, I haven’t seen any indication from Jira/Easy BI that they plan to add this functionality in a future release.
This makes me feel like they’re trying to adapt the customer to the product instead of evolving it to meet our needs. In other words, if the tool isn’t right for the job, the job shouldn’t be changed to fit the tool. Instead, we should look for a different tool.
I know your best suggestion has all the good will in it, However, it feels like it would be a workaround rather than a true solution.
Thank you very much anyway. It’s helpful to know that this functionality isn’t currently available, and it’s reassuring to know that it’s not a matter of me missing something.
Have a good day!
Thanks!