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\] 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.
* \[open\] Displaying the prefix might be costly to do as it is more than just the name of the stage/gate. It will most likely require an additional request to the backend. In the case of the table, it might require multiple requests similar as for avatars.
* The attribute can be changed via an ng-select.
* \[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?
* 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 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 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 available as a change in baseline mode?
* \[open\] Is there a date alert notification in case a work package is not finished but the gate/stage ends.
* \[open\] Is the time span the stage/gate contains indicated in the date picker of the work package? This would indicate when the work package should be worked on.
* \[open\] Should there be a hard limit regarding the dates or a message displayed if the dates are outside of the stage/gate's date range?
* \[open\] Is the attribute selectable to be displayed left/right/far right in the Gantt-Chart.
* The new functionality is hidden behind the 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\] 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.
* \[open\] Displaying the prefix might be costly to do as it is more than just the name of the stage/gate. It will most likely require an additional request to the backend. In the case of the table, it might require multiple requests similar as for avatars.
* The attribute can be changed via an ng-select.
* \[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?
* 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 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 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 available as a change in baseline mode?
* \[open\] Is there a date alert notification in case a work package is not finished but the gate/stage ends.
* \[open\] Is the time span the stage/gate contains indicated in the date picker of the work package? This would indicate when the work package should be worked on.
* \[open\] Should there be a hard limit regarding the dates or a message displayed if the dates are outside of the stage/gate's date range?
* \[open\] Is the attribute selectable to be displayed left/right/far right in the Gantt-Chart.
* The new functionality is hidden behind the feature flag developed as part of ###58159