You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 10
Next »
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?
- Research how to make the Cumulative Flow time boundary 'last 12 months' instead of by PI
Jira Key | Issue Summary | Chart | Notes |
---|
LACE-3168 | Issue counts on sparklines | Features started and closed by PI | need to re-identify which sparklines are correct |
| minor differences in issue counts | 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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Program | Issue Summary | Jira Key | Notes |
---|
EQRS | sparklines on features started and closed incorrect | LACE-3168 | need to re-identify which sparklines are correct |
EQRS | minor differences in issue counts |
| PI measures use dateBetween, JQL uses during. May need to expand PI measures by one day on either side |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Program | Issue Summary | Jira Key | Notes |
---|
EQRS | sparklines on features started and closed incorrect | LACE-3168 | need to re-identify which sparklines are correct |
EQRS | minor differences in issue counts |
| PI measures use dateBetween, JQL uses during. May need to expand PI measures by one day on either side |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|