Content
View differences
Updated by Parimal Satyal 5 days ago
**User case:**
Rules are part of a workflow. Admins define and edit them in the workflow. The same status change can follow different rules in different projects by using different workflows.
Example: Workflow "Bug workflow ALPHA" requires the field Reason for the status change to Cancelled. Workflow "Bug workflow BETA " has no such rule. ALPHA uses a variant with the first workflow, BETA uses a variant with the second. Only users in ALPHA are asked to fill out the field.
**User story:**
As an admin, I want to define different transition rules per project, so that each team works with the rules that fit its process without affecting other projects.
<br>
**Acceptance criteria:**
1. An admin can add, change and remove rules in a workflow, directly from the Workflows page
2. Rules are saved with the workflow and apply to every type and variant that uses it ~~in in all projects where they are enabled~~ enabled
3. ~~Before Before changing a shared workflow, the admin can see which types/ variants and projects use it~~ _(unrelated to transition rules)_ it
4. When a workflow is copied, its rules are copied too. Changing the copy does not change the original
5. Given ALPHA uses a workflow with the rule "Reason required for Cancelled" and BETA uses a workflow without it, when a user in ALPHA sets a work package to Cancelled without a reason, then the user is asked to fill in the field _before the transition can occur_. field. When a user in BETA does the same, then the status changes _immediately_. changes.
6. Changed rules apply from the next status change on. Existing work packages are not changed
7. After a work package is moved to another project, its status changes follow the rules of the new project _(eg. if the new project uses a different variant with a different workflow)_, project, not the old one
Rules are part of a workflow. Admins define and edit them in the workflow. The same status change can follow different rules in different projects by using different workflows.
Example: Workflow "Bug workflow ALPHA" requires the field Reason for the status change to Cancelled. Workflow "Bug workflow BETA " has no such rule. ALPHA uses a variant with the first workflow, BETA uses a variant with the second. Only users in ALPHA are asked to fill out the field.
**User story:**
As an admin, I want to define different transition rules per project, so that each team works with the rules that fit its process without affecting other projects.
<br>
**Acceptance criteria:**
1. An admin can add, change and remove rules in a workflow, directly from the Workflows page
2. Rules are saved with the workflow and apply to every type and variant that uses it ~~in
3. ~~Before
4. When a workflow is copied, its rules are copied too. Changing the copy does not change the original
5. Given ALPHA uses a workflow with the rule "Reason required for Cancelled" and BETA uses a workflow without it, when a user in ALPHA sets a work package to Cancelled without a reason, then the user is asked to fill in the field _before the transition can occur_.
6. Changed rules apply from the next status change on. Existing work packages are not changed
7. After a work package is moved to another project, its status changes follow the rules of the new project _(eg. if the new project uses a different variant with a different workflow)_,