Content
View differences
Updated by Niels Lindenthal 24 days ago
* **Improved data quality:** Ensures critical information is captured at the right workflow stages
* **Process compliance:** Enforces business rules and approval gates automatically, guides users through the process
* **Reduced errors:** Prevents incomplete or invalid status transitions
* **Flexibility:** Adapts field requirements to different issue types and workflows
**Examples of use cases**
* Specific actions (e.g. comments) may be required to change the status. For example when a ticket is set to "cancelled" an additional comment should be mandatory, so that users need to explain the reason why an issue was cancelled.
* Approval workflow: Approvals are handled by specific individuals, tied to the status.
* Defined list of checkboxes that must be checked before changing the status of a work package (e.g. task cannot be set to "closed" if all checkboxes of the Definition of Done are not checked).
* Block transitions if conditions in the WP are not met (e.g. not allowing to close a WP if some fields are not filled out).
* **Process compliance:** Enforces business rules and approval gates automatically, guides users through the process
* **Reduced errors:** Prevents incomplete or invalid status transitions
* **Flexibility:** Adapts field requirements to different issue types and workflows
**Examples of use cases**
* Specific actions (e.g. comments) may be required to change the status. For example when a ticket is set to "cancelled" an additional comment should be mandatory, so that users need to explain the reason why an issue was cancelled.
* Approval workflow: Approvals are handled by specific individuals, tied to the status.
* Defined list of checkboxes that must be checked before changing the status of a work package (e.g. task cannot be set to "closed" if all checkboxes of the Definition of Done are not checked).
* Block transitions if conditions in the WP are not met (e.g. not allowing to close a WP if some fields are not filled out).