Have you ever found yourself manually adding up the story points of all the tickets in an epic, only to realize that many of the tickets do not have an estimated sprint value?
2
-
1Epics are "really big stories" that haven't been decomposed yet. Why are you assigning stories to future Sprints, or trying to retroactively determine how many story points some decomposed epic was worth? The "why" matters, because it seems like something you shouldn't be doing in the first place. If you have a use case there may be a better approach.– Todd A. Jacobs ♦Nov 10 at 3:11
-
That's a great question. We are not assigning stories to future sprints (though I have seen that done as a way to prioritize the backlog). In this case, I think product owners are trying to figure out how much work is left in the roadmap (epic of epics).– Yvonne AburrowNov 10 at 16:13
Add a comment
|
1 Answer
This bookmarklet will add up the sprint value of all estimated tickets in the epic, tell you how many tickets do not have an estimate, and how many tickets there are in the epic.
Add a bookmark on any page to your bookmarks bar, then right-click on it and select edit
- Paste the JavaScript below in the URL field
- Edit the title field to something like “epic total”
- Test it on an epic page in Jira.
javascript:{
const elements = Array.from(document.getElementsByClassName('css-1lt331k'));
const ticketEstimates = elements.map(el => el.innerHTML);
let numOr0 = n => isNaN(n) ? 0 : n;
const numericValues = ticketEstimates.map(val => numOr0(val));
const sumOfAll = eval(numericValues.join('+'));
alert('The total value of the estimates of all tickets in this epic is ' + sumOfAll + '\n' + 'The total number of tickets in this epic is ' + numericValues.length + '\n' + 'The number of unestimated tickets in this epic is ' + numericValues.filter(x => x === 0).length);
}
The resulting alert looks like this:
-
I also considered adding a line of the script to insert the total value of the tickets into the story points field of the epic Nov 9 at 18:41