mikebowler / jirametrics Goto Github PK

• Issues will now have links to parents, and other issues, causing significant duplicates. Merge them all as best we can.
• When the same issue shows up twice but for different boards, track both boards in the issue somehow.

We currently assume that Flagged in Jira means blocked. Many teams also use an issue_link to reflect blocked and we aren't considering that.

The full noisy output should get written to a log. What shows up on the console should be easy to read.

It isn't obvious enough today why items don't show in the report. Perhaps a black dividing line or a label.

The current implementation does show items that aren't visible on the board but it's too subtle. Unmapped statuses are shown with an interrobang, deployed fix-versions are shown with a checkmark, items no longer in a sprint are shown by the absence of an active sprint. All of these should be shown in a consistent way to draw attention to the fact that nobody is seeing them and therefore, we've forgotten about them.

It's unclear if there will ever be a valid reason to merge projects from different instances but for now don't allow it. It will cause considerable confusion if keys are no longer unique.

Find some way to visualize how predictable this data is. If we did a Monte Carlo on it, how accurate would we expect the results to be?

We now support multiple different ways to be blocked. Make the chart show which one is true (Flagged, Status)

Right now, the stalled indicators don't show until 5 days after the last activity. It would be more accurate to show it as stalled right away.

None of the reports currently show WIP limits. Either add this to an existing report or make a new report.

Things we want to highlight:

• Where we exceed maximums or are under minimums
• Where we never exceed maximums or minimums (ie the max is set too high so we never hit it)

Currently each report has to be told what expedited means. This should be at the board level.

If none of the tickets are ever expedited then only two bars show on every issue. Ensure that three are always present.

If no board ids specified then scan across all included issues to find all the boards involved

We currently only return the issues referenced in the boards filter query. We need to walk any links (issue_link, parent, epic_link, sub-tasks) and download those as well. They should be marked so that they don't get included in the reports directly though.

There's a blank area to the left of 0 on the chart and I'm not sure why it's doing that. Remove this blank space.