Open justinbmeyer opened 2 months ago
Initiative A
Epic A (start date, due date)
Epic B (story points median, confidence)
Initiative A
Epic A (start date, due date)
Epic B (story points)
Initiative A
Epic A (start date, due date)
Initiative A
Epic B (story points)
Initiative A
Epic A (start date, due date)
Epic B (story points median)
Initiative A
Initiative A
Epic A (start date)
Epic B (story points median)
Initiative A
Epic A (start date)
Epic B (confidence)
Description
Calculate the amount of work complete within a parent jira issue type.
Out of Scope
Integrating the value into the UI
MVP Acceptance Criteria
bitovi-training
accountissue = IMP-143
If I open the console, there is a report showing the percentage completion of all issue types above epic. Perhaps something like:
Calculation
Total Work
Completed Work
average initiative time
Don't include partially estimated initiatives. 3 epics have an estimate, but 1 does not.
What if there are no initiatives that are estimated or timed? Average initiative should 6 weeks.
estimated time adjusted for confidence
We need to inflate estimates with a confidence factor (driven by a log-normal distribution).
We should pass some functions that we can later fill in. I think we should use similar function signatures to what the autoscheduler uses: https://github.com/bitovi/jira-auto-scheduler/blob/main/public/schedule-prepare-issues.js#L13
The implementation might look a lot like: https://github.com/bitovi/jira-auto-scheduler/blob/main/public/schedule-prepare-issues.js#L119
Implementation Suggestions
The easiest place to start would be to create a function in a new JS file ... something like
public/percent-complete/percent-complete.js
.Import that function in
/public/timeline-report.js
and call it here:https://github.com/bitovi/jira-timeline-report/blob/main/public/timeline-report.js#L781
I would use the
issues
format instead offormatted
. There's a reason why I simplified it previously (b/c I used to use excel), but I should have bit the bullet earlier and used what Jira gives back. Also, you should be able to read the issue hierarchy (instead of making assumptions).percentComplete
would calculate the percent complete on every issue. It should take configuration arguments above.You'll need to set up a tiered parent/child relationship.
Then you'll start on the "epic" level and calculate all the "known" epics.
You'll then need to move up one level (initiatives).
On
initiatives
you'll need to calculate and use anaverage
initiative size for "unestimated" initiatives. You'll need to repeat this for every part of the topology.