Page History

General:

How do we handle ongoing maintenance of PI dates
All programs have inactive teams, dirty projects
Backlog comp charts relies on tags, not work item types
Most projects have inactive teams. Can we create new project categories so we can avoid custom measures like "EQRS ART Teams"
How can we have RTEs input Jira data so PI measures are not a LACE support request?
- create an epic with Start/End dates?
- EQRS uses a release per PI. Can we use it? What are other programs doing?
Research how to make the Cumulative Flow time boundary 'last 12 months' instead of by PI

...

Horizontal Navigation Bar

Horizontal Navigation Bar Page

title	Global Issues

#	Jira Key	Severity	Chart	Issue Summary

Chart

Notes

Notes

1

LACE-3168

High

Features started and closed by PI

Closed Issues count w/in PI are wrong

Features started and closed by PI

Closed Issues measure calculates cumulative results, rather than closures w/in the PI date boundaries

minor differences in issue counts


2		High	All Reports using PI date measures

PI measures use dateBetween, JQL uses during. May need to expand PI measures by one day on either side

minor differences in issue counts	EazyBi Standard measures results differ from Jira Queries
3		Medium	Features in Status by PI	Time Member Lags by one period

Features in Status by PI

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

Custom Start date and PI Measures


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. 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

Page tree

Versions Compared

Old Version 11

New Version 12

Key