Use start and due date attributes when listing iterations
What does this MR do and why?
Background
The changes in this MR are behind a feature flag (iteration_cadences
).
Iterations can be generated automatically for an iteration cadence.
When iterations are created, their titles have hardcoded start and due dates e.g., Iteration 1: Oct 1, 2021 - Oct 3, 2021
.
We won't be hardcoding the dates in the backend and we are updating the frontend components to use the date attributes for display.
The backend portion will merge after this MR. This MR completes the frontend tasks laid out in #343523 (closed).
Changes introduced in this MR
Use iteration start/due dates attributes to display them in
- the iteration cadence list
- iteration select dropdown
- in the issue sidebar
- in the board issue sidebar
- in the issue list bulk edit sidebar
- in the board list create form
- in the iteration board list header
Screenshots (before/after)
Iteration cadences list
Before | After |
---|---|
Issue sidebar / Board issue sidebar / Issues list bulk edit / Board list create form
Board List header
How to set up and validate locally
-
Enable the iteration cadences feature
Feature.enable(:iteration_cadences)
-
Create a new iteration cadence for a group (ex.
gitlab-org
) -
Visit these locations to see the changes
- Iteration cadence list: http://gdk.test:3000/groups/gitlab-org/-/cadences
- Issue sidebar (visit any issue page under the group)
- Issue bulk edit sidebar (it appears when you click
Edit Issues
in Issues List - Board issue sidebar (visit any board under the group)
- Board list create form (click
Add List
in Board) - Board list header for an iteration list after adding it in the previous step.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.