| # | Jira Key | Severity | Done | Chart | Issue Summary | Notes |
|---|
| 1 | LACE-3168 | High | Done | Features started and closed by PI | Closed Issues count w/in PI are wrong | Closed Issues measure calculates cumulative results, rather than closures w/in the PI date boundaries |
| 2 |
| High |
| All Reports using PI date measures | Minor differences in issue counts | EazyBi Standard measures results differ from Jira Queries |
| 3 |
| Medium | Done | Features in Status by PI | Time Member Lags by one period | When Using the PI Start Date Measures For Open Issues measure(and presumably all other counts), the implementation numbers are correct but show the value from the previous PI for each PI on the chart |
| 4 |
| Medium |
| All Reports using PI date measures | Eliminate Custom Start date and PI Measures | Identify a solution for getting PI Start/End date from Jira and eliminate program specific custom measures. EQRS creates a releases for each PI.(fix version Start date measure) Need to find out what other programs are doing |
| 5 |
| High |
| All | Programs have inactive teams | Inactive teams forces us to select individual team projects, requiring maintenance (removal or addition of projects) to the data import to maintain accurate issue counts for charts aggregating data from all program teams. Project Categories could be used or Project Labels (if they exist) |
| 6 |
| Low |
| Cumulative Flow | Time Period changes with PI selection | Should show a 12 month window. Because time is in Rows, its taking the value from the time dimension current member selection. We cannot use the 12 month time dimension member because PI selection is a common page element. We need a custom measure (in measures dimension) to fix 12 months |
| 7 |
| Medium | Done | Features Started and Closed by PI | Removed Issue Histories Closed Line | The red line shows cumulative issues count, which is not particularly valuable and creates confusion. This will require a customized measure |
|
| Low |
| Program backlog health | Aggregate statuses | The statuses are individually selected and there are more statuses that include items in the New to ready status domains |
|
| Medium |
| All | Granular aggregate statuses | We have aggregated all statuses into the proposed user story workflow statuses, but to provide more granular reporting on program backlog, we may need specific aggregations to support more awesomerness |
|
| Low |
| Program Wide Backlog composition | Random issues not showing in EazyBI but in Jira Validation Query | Issues EQRSMD-12, EQRSMD-20, EQRSMD-32, EQRSPRTL-46 are not showing up in Eazy but show up in a Jira validation query. EQRSMD-12, EQRSMD-20, and EQRSMD-32 were migrated from a different project and changed from task to a story, but EQRSPRTR-46 has no anomalous history changes, but was resolved on the day of the report |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ISG Playbook
APIs