Features used to implement the example
Example: Prevent issue creation if another issue with same field value already exists
We want to prevent issue creation when there is already another issue in the project with the same value in a certain field. That field works as a kind of alternative issue key in the project. You can easily extend this example to much more complex cases, like preventing coincidence of values in more than one field at the same time, or in more than one project, all projects in a category, or in all the projects in Jira.
Let's suppose that we have a Text custom field called Invoice, and we want to avoid this field's value to be repeated among issues of same issue type in same project, i.e., we don't want to have two issues with same issue type, in same project and same value in field Invoice.
We are going to introduce a validator Validation based on JQL query in transition "Create Issue" with the following configuration:
JQL Query: project = "%{00018}" AND issuetype = "%{00014}" AND Invoice = "%{10200}"
Note that:
- %{00018} is the field code for Project key
- %{00014} is the field code for Issue key
- %{10200} is the field code for custom field Invoice. This field code depends on each particular Jira instance
Once configured, transition “Create Issue” will look like this:
Alternative implementation
There is an alternative implementation based on validator Boolean condition and validator with math. date-time or text-string terms. The following configuration should be used:
Boolean expression is: count(issuesFromJQL("project = '" + %{00018} + "' AND issuetype = '" + %{00014} + "' AND Invoice = '" + %{10200} + "'")) = 0
Note that:
- %{00018} is the field code for Project key
- %{00014} is the field code for Issue key
- %{10200} is the field code for custom field Invoice. This field code depends on each particular Jira instance
Once configured, transition “Create Issue” will look like this:
Other examples of that function
Condition and validation based on JQL query
- Make linked issues, sub-tasks and JQL selected issues progress through its workflows
- Prevent issue creation if another issue with same field value already exists
Boolean condition and validator with math. date-time or text-string terms
- 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
