Content
View differences
Updated by Jens Ulferts over 1 year ago
**As** a project member
**I want to** assign to and see the assignment of a work package to a stage/gate
**so that** I can better understand the context the work package is in.
Assumes ###58159 is done.
**Acceptance criteria**
* Work pages receive a new attribute: The gate/stage they belong in.
* \[open\] What is the name of the attribute?
* \[open\] Can a work package be assigned to multiple stages?
* \[open\] If so, are there any limitations, e.g. that a work package can only be assigned to consecutive stages?
* \[open\] If the work package dates are limited by the associated stage/gate, are they then limited to the interval created by the min of the associated stages and the max of the associated stage?
* \[open\] Can a work package be assigned to a gate (checklist items)?
* The attribute can be administrated same as every other attribute (e.g. status, assignee, version).
* It can be moved in and out of an attribute group.
* \[open\] Should this be an attribute that is seeded? If so, which group should it be seeded into?
* \[open\] Should existing installations get the attribute activated for their existing types? Assumption - no.
* The attribute's value is displayed including the colored type indicator prefix in both the split/full view as well as the table.
* \[Technical detail\] Depending on \[open\] Displaying the API prefix might be costly to be designed, the type of the lifecycle element (stage or gate) is or is not encoded in the API response for a work package. If do as it is encoded, e.g. inside more than just the URL, then name of the only remaining part stage/gate. It will most likely require an additional request to be known is the color. That is by now part backend. In the case of the custom\_styles.css so table, it can be taken from there.
If the API does not encode the type in the url, then especially displaying the different icons in the table will be difficult. might require multiple requests similar as for avatars.
* The attribute can be changed via an ng-select.
* \[Technical detail\] \[open\] Getting the data for displaying the prefix should be simpler here, but it will require coding a variation of the autocompleter.
* The attribute can be added as a column to the work package list.
* The table can be ordered and grouped by that column. The order is not by name of the gate/stage but by the order the gate/stages are in.
* \[open\] In case a work package can be assigned to multiple stages/gates.
* What is the correct order?
* \[Assumption\] Stages and gates already have an order so work packages assigned to a stage/gate should use that order.
* \[open\] What if a work package is assigned to multiple stages/gates.
* What is the correct grouping?
* The attribute can be used as a filter.
* \[open\] What are the operators available? Assumption: 'is (or)', 'is not', 'is empty' and 'is not empty'.
* \[open\] What \[open\] What are the values available? The stages/gates active in the current project or those in the current project and its descendants? The current behaviour with all of the other fields is to only shows those of the current project. If the filter is used in the global list, all stages/gates should be shown.
* \[open\] Should there be stages/gate specific filters to be able to have filters like: 'Work packages which's gate is in 5 days'? Assumption - no.
* The attribute is journalized.
* \[open\] Which messages are printed in the activity? printed.
* In case the associated gate/stage is later disabled in the project administration, the value is no longer displayed, changes are not shown in the journal and the work package are not found via filters (see ###58163).
* The API v3 has a dedicated resource for Stages/Gates.
* GET endpoint for referencing selected stages/gates.
* GET endpoint for selecting all available (active) stages/gates of the project when selecting the value of the attribute.
* \[open\] Is the attribute selectable to be displayed left/right/far right available as a change in the Gantt-Chart. baseline mode?
* The new functionality \[open\] Is there a date alert notification in case a work package is hidden behind not finished but the feature flag developed as part of ###58159
**Out of scope**
* Showing changes when activating the work package baseline comparison. gate/stage ends.
* Indicating \[open\] Is the time span the stage/gate spans contains indicated in the date picker of the work package.
* package? This would indicate when the work package should be worked on.
* \[open\] It could also \[open\] Should there be done as a message in the datepicker stating that the current dates are not matching the dates of the stage the work package is associated to.
* Date alert notification in case a work package is not finished but the gate/stage ends.
* A hard limit regarding the dates or a message displayed if the dates are outside of the stage/gate's date range.
range?
* This would also require rescheduling a work package \[open\] Is the attribute selectable to be displayed left/right/far right in case the stage/gate's dates are changed. The complexity of this would be quite high.
Gantt-Chart.
* Displaying The new functionality is hidden behind the stage/gate time span inside the gantt chart. feature flag developed as part of ###58159
**I want to** assign to and see the assignment of a work package to a stage/gate
**so that** I can better understand the context the work package is in.
Assumes ###58159 is done.
**Acceptance criteria**
* Work pages receive a new attribute: The gate/stage they belong in.
* \[open\] What is the name of the attribute?
* \[open\] Can a work package be assigned to multiple stages?
* \[open\] If the work package dates are limited by the associated stage/gate, are they then limited to the interval created by the min of the associated stages and the max of the associated stage?
* \[open\] Can a work package be assigned to a gate (checklist items)?
* The attribute can be administrated same as every other attribute (e.g. status, assignee, version).
* It can be moved in and out of an attribute group.
* \[open\] Should this be an attribute that is seeded? If so, which group should it be seeded into?
* \[open\] Should existing installations get the attribute activated for their existing types? Assumption - no.
* The attribute's value is displayed including the colored type indicator prefix in both the split/full view as well as the table.
* \[Technical detail\] Depending on
If the API does not encode the type in the url, then especially displaying the different icons in the table will be difficult.
* The attribute can be changed via an ng-select.
* \[Technical detail\]
* The attribute can be added as a column to the work package list.
* The table can be ordered and grouped by that column. The order is not by name of the gate/stage but by the order the gate/stages are in.
* \[open\] In case a work package can be assigned to multiple stages/gates.
* What is the correct order?
* \[open\] What if a work package is assigned to multiple stages/gates.
* What is the correct grouping?
* The attribute can be used as a filter.
* \[open\] What are the operators available? Assumption: 'is (or)', 'is not', 'is empty' and 'is not empty'.
* \[open\] What
* \[open\] Should there be stages/gate specific filters to be able to have filters like: 'Work packages which's gate is in 5 days'? Assumption - no.
* The attribute is journalized.
* \[open\] Which messages are printed in the activity?
* In case the associated gate/stage is later disabled in the project administration, the value is no longer displayed, changes are not shown in the journal and the work package are not found via filters (see ###58163).
* The API v3 has a dedicated resource for Stages/Gates.
* GET endpoint for referencing selected stages/gates.
* GET endpoint for selecting all available (active) stages/gates of the project when selecting the value of the attribute.
* \[open\] Is the attribute selectable to be displayed left/right/far right
* The new functionality
**Out of scope**
* Showing changes when activating the work package baseline comparison.
* Indicating
*
* Date alert notification in case a work package is not finished but the gate/stage ends.
* A hard limit regarding the dates or a message displayed if the dates are outside of the stage/gate's date range.