Properly handle state for closed iterations
Problem
This iterations is closed (https://gitlab.com/groups/gitlab-org/-/iterations/1) but the issue list is still showing things as in progress. One issue was closed this week and it changed the percent complete. Once an iteration is closed, the report should be frozen to preserve historical accuracy of what was and what was not completed in a given iteration.
Job Story
When viewing an Iteration that is closed, I need to see historically accurate information about what was completed and not completed in a given Iteration, so that I can have immutable benchmarks to help me understand how we are improving over time.
Proposal
- The complete and incomplete metrics should be immutable once an iteration is closed
- Showing different metrics in the top section - "completed", "incomplete" - or something to provide a quick snapshot of plan vs. actual.
- When toggling the unit filters, the complete and incomplete metrics update accordingly.
- When an Iteration is done, the metrics at the top and the charts are immutable
UX
Availability and Testing
Ensure test coverage in unit/integration tests.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.