# Feature AGILE-60 - Provide created vs. resolved chart Project: Stream agile Status: in test URL: https://community.openproject.org/work_packages/AGILE-60 ## Planning | Attribute | Value | | --- | --- | | Date | | | Priority | Medium | | Target versions | 18.0.0 | | Sprint | Sprint 13 | | Backlog bucket | | | Votes | | | List | RM Agile, Agile Reporting | | Roadmap | 2026 Q4 | | Relevance | | ## OPEN POINTS / FEEDBACK _No work packages_ ## Features and Chunks | ID | Subject | Type | Status | Assignee | Target versions | Spent time | | --- | --- | --- | --- | --- | --- | --- | | AGILE-490 | Created vs resolved as line charts with filled area | Implementation | closed | | 18.0.0 | | | AGILE-491 | Created vs resolved time span increased to 7 sprints & no non-working days | Implementation | closed | | 18.0.0 | | | AGILE-492 | Performance improvement on created vs resolved | Implementation | new | | 18.0.0 | | ## Bugs and other work packages _No work packages_ ## Technical Details | Attribute | Value | | --- | --- | | Module | | | Feature Flag | | | Requires doc change | No | | Enterprise plan | Enterprise / Professional (PRO) | ## Details | Attribute | Value | | --- | --- | | Pull preview | | | Mockups | https://www.figma.com/design/owpxg3fdqZONIGL6SBSG8M/Agile--Sprint-reports?node-id=1-78965&t=lrfXIMsRG30oJ3B8-1 | | Accessibility | No | ## People | Attribute | Value | | --- | --- | | Assignee | Ivana Šugić | | Accountable | | | Product manager | Rosanna Sibora | | Developers | Aileen Ketzler, Tobias Dillmann | | Designer | Julia Racsko | | Ordered by | | | Signed off by | | | Interest by | | ## Estimates and progress | Attribute | Value | | --- | --- | | PD (min) | | | PD (max) | | | Work | 30d 0h · Σ 30d 0h | | Labor costs | | ## Description As an agile coach I would like to understand my teams' expected and possible workload so that we can plan sprints better. The purpose of the created vs resolved chart is to visualize whether the team is able to keep up with the work packages added to the project: * if the created data series is higher than the resolved data series: work is piling up * if the created data series and the resolved data series match: team is keeping the added features in check * if the resolved data series is higher than the created data series: the team is reducing the work Because those conclusions can only be made when observing over a longer period of time, the scope extends the one sprint which is why all work packages of the project are considered and not only those of the sprint. **Acceptance criteria:** * The charts automatically shows as a part of a sprint report (both completed and active sprints) * Is a two dimensional line chart * axis: * y: number of work packages * x: time * The time span is that of the current sprint together with the time span of the 6 preceding sprints (same as for the velocity chart) * If there are less than 6 preceding sprints, show less. As a minimum, the sprint's time span is displayed. * Sprint's time span is the planned time until that is replaced by the sprints actual start and completion time. * The granularity is days  * data sets: * Created (color red): * work packages added to the project at this point in time. The scope is explicitly the project, not only the sprint. * The value is cumulative. Meaning that if at the first point in time a work package is created, the data set will have the value of 1. If then on the subsequent point in time another work package is created, the value will be 2. If no work package is created, the value stays at 1. It does not drop unless a work package is removed from the project. * The above means that the number of work packages that existed before the chart's time span needs to be subtracted form the number of work packages at any given time during the time span of the sprint. * If more work packages are removed from the project (e.g. moved to a different project) than are added, the data set might have negative values. Edge case * Resolved (color green): * work packages resolved in the project at this point in time. The scope is explicitly the project, not only the sprint. * A resolved work package is one that has any of the statuses configured in backlogs to be considered closed. * The value is cumulative.  Meaning that if at the first point in time a work package is closed, the data set will have the value of 1. If then on the subsequent point in time another work package is closed, the value will be 2. If no work package is closed, the value stays at 1. It does not drop unless a work package is reopened. * The above means that the number of work packages that were closed before the chart's time span needs to be subtracted form the number of closed work packages at any given time during the time span of the sprint. * If more work packages are reopened in the project than resolved, the value might become negative. Edge case. * Fill: * The area between the two data sets is filled. The color of this depends on whether the created or resolved is higher at this point in time: * If created is higher than resolved: red * if resolved is higher than created: green * ~~Non working days are displayed (see burndown)~~ Don't show non-working days * The time span of the sprint the report is shown for is displayed. e.g. by another background or by vertical lines * TODO: @Julia Racsko, desgin needed. **Technical notes:** [Chart.js should allow displaying such a graph](https://www.chartjs.org/docs/latest/samples/area/line-datasets.html) This is a technical reference not a mockup/example of how the created vs.resolved chart should look.

**Out of scope:** * Showing the dates as a table under the chart * Desired, but unclear if this is the right place (what if it's 4 weeks long? What is it's just 1/4 width of the page?) * Projection line