Since features usually represent tasks that needs to be completed by various stakeholders and task owners.
There are cases in which tasks become irrelevant and therefore the system closes them automatically.
For example:
- Equivalent tasks were opened for multiple users, but the process requires the completion of only one/x of them.
In this case the parent idea/project can move automatically to the next state of the workflow and the remaining tasks becomes non relevant.
This is usually relevant for features like expert reviews, risk assessments etc. - The parent idea/project was already rejected/closed, and there is no need to process its sub tasks.
To support this feature entities can be configured to automatically change their state when their parent initiative moves to a specific state.
How does it work?
The logic is based on the new state of the parent initiative, regardless of its previous state.
A rule can be defined as follows:
When the parent initiative moves to State X → move its child feature entities to State Y.
There is no reference to the initiative's original state or the state it moved from.
Multiple rules can be configured for feature entities.
The default setting is the following:
When an initiative moves to Duplicate or the last state in the idea/project workflow → its feature entities automatically move to Canceled.
When an initiative is deleted → its feature entities are deleted as well.
Important Notes
- Last state is dynamic and always refers to the last state currently defined in the idea/project workflow.
- Different rules can be configured for different feature types. However, currently the same configuration is applied to all features.
- In case you would like to change this setting, please contact your CSM.