[AGILE-304] Work package tables (completed, unfinished & changed) on sprint report page - #24666
Draft
toy wants to merge 2 commits into
Conversation
toy
force-pushed
the
feature/agile-304-work-package-tables-completed-unfinished-and-changed-on-sprint-report-page
branch
from
August 27, 2026 20:04
7672c99 to
b3a062d
Compare
toy
changed the base branch from
dev
to
feature/agile-303-work-package-overview-on-sprint-report-page
August 27, 2026 20:04
toy
force-pushed
the
feature/agile-304-work-package-tables-completed-unfinished-and-changed-on-sprint-report-page
branch
from
August 28, 2026 19:35
b3a062d to
953bbad
Compare
EinLama
force-pushed
the
feature/agile-303-work-package-overview-on-sprint-report-page
branch
2 times, most recently
from
September 4, 2026 09:24
555c023 to
e2d8bff
Compare
myabc
added this pull request to stack #25313
September 14, 2026 13:45
myabc
removed this pull request from stack #25313
September 14, 2026 13:46
EinLama
force-pushed
the
feature/agile-303-work-package-overview-on-sprint-report-page
branch
2 times, most recently
from
September 16, 2026 08:19
9760adf to
ad977bc
Compare
Base automatically changed from
feature/agile-303-work-package-overview-on-sprint-report-page
to
dev
September 16, 2026 12:00
toy
force-pushed
the
feature/agile-304-work-package-tables-completed-unfinished-and-changed-on-sprint-report-page
branch
from
September 18, 2026 20:01
953bbad to
3e3d8b0
Compare
…sprint report page
Follows ###AGILE-296
**As** an agile user
**I want to** have tables listing work packages of different criteria
**so that** I can understand the sprint's work package state in more
depth
* The sprint report page has four work package tables as widgets
* "Completed work packages"
* Work packages associated to the sprint that are finished
* Reference date: sprint finish date or current date (earlier one)
* "Unfinished work packages"
* Work packages associated to the sprint that are not finished
* Reference date: sprint finish date or current date (earlier one)
* "Scope increase after sprint start"
* Work packages added from the sprint after the sprint start date
* If the sprint start date is in the future show a blank slate
stating: "Work packages will appear here after the sprint starts."
* "Scope removal after sprint start"
* Work packages removed from the sprint after the sprint start date
* If the sprint start date is in the future show a blank slate
stating: "Work packages will appear here after the sprint starts."
* If dates are not set for the sprint, blankslates are shown.
* Each of those work package tables are
* baseline table if the reference date is a sprint start or finish
date
* non baseline table if the reference date is the current date
* The widget is only displayed if the instance has an EE pro license
* "Finished" always refers to the work packages that have a status
considered closed in the project (backlogs settings)
* The widgets should always cover the full width
* While the sprint start and finish dates are dates (without time zones)
the current user's local time for start or end of the day of that date
is used.
* The widget will be EE (pro) only. Because of that, all users able to
access the widget will have access to the baseline feature which is EE
(basic).
* View sprints (and by that view work packages) is required.
* Configuring the widgets
https://community.openproject.org/wp/AGILE-304
toy
force-pushed
the
feature/agile-304-work-package-tables-completed-unfinished-and-changed-on-sprint-report-page
branch
from
September 18, 2026 20:15
3e3d8b0 to
b3e1712
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ticket
https://community.openproject.org/wp/AGILE-304
What are you trying to accomplish?
Screenshots
What approach did you choose and why?
Merge checklist