Page History
Section | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Example: Restrict sub-task type creation depending on parent issue status conditions
We want to restrict sub-task type creation depending on parent issue status:
- If parent status is "Open" we only allow sub-tasks types "Sub-task_type_1", "Sub-task_type_2", and "Sub-task_type_3".
- If parent status is "Resolved" we only allow sub-tasks types "Sub-task_type_1", and "Sub-task_type_4".
- If parent status is different from "Resolved" and "Open" sub-task creation is not allowed.
We would use the following configuration of Boolean validator with math, date-time or text-string terms:
The boolean expression used: (%{00042} = “Open” AND (%{00014} = “Sub-tasks_type_1” OR %{00014} = “Sub-tasks_type_2” OR %{00014} = “Sub-tasks_type_3”)) OR (%{00042} = “Resolved” AND (%{00014} = “Sub-tasks_type_1” OR %{00014} = “Sub-tasks_type_4”))
Note that:
- %{00042} is field code for "Parent's issue status"
- %{00014} is field code for "Issue type"
Once configured, the transition will look like this:
Other variation of the usage example
Let 's us suppose that we replace restriction 3 with:
"If parent status is different from "Resolved" and "Open" any sub-task type is allowed."
In that case, the following configuration will do the task:
The boolean expression used: (%{00042} = “Open” AND (%{00014} = “Sub-tasks_type_1” OR %{00014} = “Sub-tasks_type_2” OR %{00014} = “Sub-tasks_type_3”)) OR (%{00042} = “Resolved” AND (%{00014} = “Sub-tasks_type_1” OR %{00014} = “Sub-tasks_type_4”)) OR (%{00042} != “Open” AND %{00042} != “Resolved”)
Note that:
- %{00042} is field code for "Parent's issue status"
- %{00014} is field code for "Issue type"
Once configured, the transition will look like this:
Other examples of that function
Incoming Links | ||||
---|---|---|---|---|
| ||||
Related Usage Examples
Content by Label | ||||
---|---|---|---|---|
|