Example: Restrict sub-task type creation depending on parent issue type
I suppose that you have one issue task called "Sub-task" and you want to restrict its creation only to "Task" parent issue types. In that case you have to add validator to transition "Create Issue" of the workflow used by "Sub-task", with the following configuration:
Text to be parsed is: %{00014} = "Sub-task" IMPLIES %{00040} = "Task"
Note that:
- %{00014} is field code for "Issue type"
- %{00040} is field code for "Parent's issue type"
- Logical connective IMPLIES is available since version 2.1.22. If you have installed a previous version, you can use the following equivalent expression: %{00014} != "Sub-task" OR %{00040} = "Task"
Once configured, transition Create Issue will look like this:
Other variation of the usage example
Avoid any type of sub-task creation only to parent issue types "Bug" and "Enhancement"
%{00041} = null IMPLIES %{00040} not in ["Bug", "Enhancement"]
being %{00041} field code for field "Parent's issue key"
an equivalent expression without using connective IMPLIES and operator NOT IN:
%{00041} != null OR %{00040} != "Bug" AND %{00040} != "Enhancement"
Avoid "Sub-task" type creation only to parent issue types "Bug" and "Enhancement"
%{00014} = "Sub-task" IMPLIES %{00040} not in ["Bug", "Enhancement"]
or an equivalent expression without using connective IMPLIES and operator NOT IN:
%{00041} != "Sub-task" OR %{00040} != "Bug" AND %{00040} != "Enhancement"
Limit "Sub-task" type creation only to parent issue type "Task", and "Agile Sub-task" type creation only to parent issue types "Story" and "Epic"
(%{00014} = "Sub-task" IMPLIES %{00040} in ["Task"]) AND (%{00014} = "Agile Sub-task" IMPLIES %{00040} in ["Story", "Epic"])
or an equivalent expression without using connective IMPLIES and operator IN:
(%{00014} != "Sub-task" OR %{00040} = "Task") AND (%{00014} != "Agile Sub-task" OR %{00040} = "Epic" OR %{00040} = "Story")
Other examples of that function
- Block a transition until all sub-tasks have certains fields populated
- Block an epic's transition depending on linked issues status and due date
- Block or hide a transition for an issue depending on its issue links
- Block or unblock a transition after an issue rested a specific time in a status
- Block transition until all sub-tasks are in a specific status category
- Close parent issue when all sub-tasks are closed
- Enforce a field (Select List) to be set when another field (Radio Button) has a certain value (works with any kind of field type)
- Ensure that all issues linked with a certain issue link type have "Due Date" field set
- If field A is populated then, field B must also be populated
- Limit issue creation per role and issue type
- Limit the number of hours a user can log per day
- Limit valid dates for work logs
- Make "Time Spent" field required when there is no time logged in the issue
- Make a custom field mandatory when priority is "Critical" or "Blocker" and issue type is "Incident"
- Make attachment mandatory depending on the value of certain custom field
- Make different fields mandatory depending on the value of a Select List custom field
- Make linked issues, sub-tasks and JQL selected issues progress through its workflows
- Make parent issue progress through its workflow
- Prevent issue creation if another issue with same field value already exists
- Reject duplicated file names in attachments
- Require at least one sub-task in status "Resolved" or "Closed" when "Testing required" is selected in Check-Box custom field
- Require issue link when resolving as duplicate
- Restrict parent issue from closing if it has sub-tasks that were created during a given parent issue status
- Restrict sub-task type creation depending on parent issue status
- Restrict sub-task type creation depending on parent issue type
- Set a condition in a global transition which only applies in a certain status
- Validate a custom field "Story Points" has been given a value in Fibonacci sequence
- Validate compatible values selection among dependent custom fields
- Validate only issue links created in transition screen
- Validate that multi-user picker custom field A does not contain any user in multi-user picker custom field B
- Validation and condition based on time expressions
- Validation based on the value of a date type project property
- Validation on issue attachments
- Validation on MIME types of issue attachments
- Validation on sibling sub-tasks depending on issue type and status
- Validation on the value of a Cascading Select field