Use cases

Block transitions on weekends or any other day of the week.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

(cog) 

jiraExpression()

Create automatically a sub-task for each selected user in a User Picker (multiple users) field of the transitioned issue.

Create issue

(cog) 

Add a comment to an issue mentioning the assignee.

The comment will only be added, if the issue priority is set to "High" or "Highest" to ensure that the assignee will only be alerted for the important issue

Add comment

(cog) 

When a story is approved, two sub-tasks for Development and QA will be created.

Create issue

Make sure that the current user has uploaded a attachment during the transition. 

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

Evaluate if work has been logged in a sub-task to prevent transitioning the parent issue when no work has been logged.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

(cog) 

Execute remote action

(cog) 

Add a formatted comment to the current issue.

It would be convenient in case that you need to create a table or highlight some important points in the comment.

Add comment

(cog) 

getMatchingValue()

Update fields

(cog) 

Execute remote action

(cog) 

Execute remote action

(cog) 

Each time a new software requirement was created in a Jira project, the functionality automatically adds all project developers as watchers. As a result, the development team is immediately informed of the new requirements, enabling better coordination and timely implementation.

Add or remove watchers

(cog) 

Once a sub-task is created, the functionality automatically adds all watchers of the parent issue as watchers to the sub-task. In this way, it becomes possible to ensure that the watchers of the parent issue remain informed of new developments and updates at the sub-task level and maintain a comprehensive overview.

Add or remove watchers

(cog) 

Update a number field with the difference in days between two dates obtained from two Date Picker fields.

Update fields

⚙️

Assign the issue to the user who last commented on the issue.

Update fields

(cog) 

Add three days to a Date Picker field from the current date.

Update fields

(cog) 

getNameFromAsset()

getAttributeFromAsset()

userDisplayName()

In our Jira Service Management project, we want to automatically send an email to the project manager to inform him of an incident in a system managed asset. 

Send email

(cog) 

matches()

Creating many issues and adding a summary and a description can be a bit frustrating and time-consuming.

To avoid such things, the following use case shows you how to create a sub-task with a summary to check for attachment type in the parent issue.

Create issue

Not allow a resolution to be set.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Fields required

Fields required or changed

(cog) 

Set the priority of the parent issue to the priority of the current issue.

Update fields

⛭ 

getMatchingValue()

Update fields

When a service request is submitted in the HR project, three IT tasks for providing the necessary work equipment are automatically created in the IT project, with the HR group added as watchers to ensure a structured and trackable onboarding process.

Execute sequence of actions

(cog) 

Keep your team on track and up to date by creating a sub-task mentioning the assignee's full name and with issue links linked to the appropriate issue whenever a high priority issue has been moved to the status "Review"

Create issue

(cog) 

Execute remote action

(cog) 

dateTimeToString()

Execute remote action

Current user must be reporter.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Compare two values condition

Compare two values validator

Make sure that the current user has uploaded a attachment during a definite period of time.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

(cog) 

When a sub-task is transitioned to the "In Progress" status the parent issue will be transitioned to the "In Progress" status as well if it is still in the "To Do" status.

Transition issue

(cog) 

Create a sub-task, set the summary based on the parent's component, and set the assignee to the current user.

Create issue

⚙️

A comment will be added to the current issue with links to the attachments included recently.

Add comment

(cog) 

When an issue is resolved and the resolution set to "Done" the Affects version/s will be added to the Fix version/s field.

Update fields

(cog) 

Automatically execute the "Start progress" transition if the issue's assignee is the project lead.

Transition issue

Make a field required to enable a transition only for issues with the story issue type.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

(cog) 

Anytime a new issue is created in the "Project Management" Jira project, the functionality automatically adds the project lead as an observer. The project lead is thereby kept up to date with all new updates and information within the project, facilitating effective monitoring and management.

Add or remove watchers

(cog) 

Add a comment to the linked Epic including the summary and status of the current issue.

This is helpful when you don't want to keep track of individual Stories and only receive notifications of the linked Epic (e.g. as a watcher or reporter).

Add comment

(cog) 

Execute remote action

Require a at least one component.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Fields required

Fields required or changed

Check whether an epic has all issues under it in a certain status.

This is particularly important if you want to block an epic as long as work is still being done on related sub-tasks.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

(cog) 

nthElement()

Create multiple sub-tasks with different summaries and descriptions.

Create issue

(cog) 

Execute remote action

(cog) 

Execute remote action

(cog) 

Update an locked issue in the Done status

Update fields

(cog) 

append()

fieldValue()

linkedIssues()

toStringList()

In our Jira Service Management project, we want to automatically add the reporter of an incident to the corresponding problem ticket.

Update fields

(cog) 

The transition to start progress on the current issue will be executed directly after its creation.

Transition issue

(cog) 

When a sub-task is closed, the labels of the sub-task will be added to the Labels field of the parent issue.

Update fields

(cog) 

Create a sub-task only if the priority of the current issue is "High".

Create issue

Evaluate a Date Picker field and block the transition if it has not been updated.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

Update fields

Evaluate issue links and hide transitions based on the outcome.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

Evaluate if a user has logged more than a certain amount of time in the latest worklog.

Jira expression condition

Jira expression validator

(cog) 

Execute remote action

Check whether the current issue is in a particular status.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

⚙️

When an issue is created without an assignee selected, the issue will be assigned to the project lead of the project.

Update fields

(cog) 

Execute remote action

(cog) 

Send an email to the current assignee only if the priority is set to "Highest" or "High".

Send email

Evaluate different values of the issue in the Parent Link field of the transitioned issue.

This use case is valid for both conditions and validators . The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

(cog) 

Often it can be useful to notify specific users about certain changes. For example, if an issue reaches a specific status, it can come in handy to get a notification about this update.

In this ise case an email will be send to the reporter, assignee and the project lead, if a specific transition has been executed.

Send email

(cog) 

union()

toStringList()

Update fields

Transition issue

(cog) 

When a sub-task is created, its summary, issue key and date, and time of creation will be added to the description of the parent issue.

Update fields

(cog) 

dateTimeToString()

Set any date field of an issue to a future date.

Update fields

(cog) 

When an issue is raised with a"Blocker" priority, a transition escalating the issue will be executed immediately after its creation.

Transition issue

(cog) 

Update the sub-task's assignee from its parent

Update linked issue or sub-task

Evaluate the comments and block transitions based on the outcome.

This use case is only valid for validators as it involves making changes during a transition. An additional error message can be added.

Jira expression validator

(cog) 

Execute remote action

(cog) 

dateTimeToString()

first()

fieldValue()

issueKeysToIssueList()

Ensure a strict task sequence by scheduling four subtasks one week apart, each blocked by the previous one. This guarantees controlled execution and clear dependencies.

Execute sequence of actions

(cog) 

dateTimeToString()

Set a Date Time Picker field to the current date

Update fields

(cog) 

Add a comment to the parent issue including the summary and status of the current issue.

This is helpful when you don't want to keep track of individual sub-tasks and only receive notifications of the parent issue (e.g. as a watcher or reporter).

Add comment

(cog) 

Create sub-tasks and link them to the parent or current issue that has a specific priority of your choice.

Create issue

Evaluate the type of files in the Attachments field.

This use case is valid for both conditions and validators . The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

(cog) 

After an incident is rejected, the functionality automatically removes all watchers from the issue. This guarantees that no other people remain in the information loop for the rejected issue, streamlining communication and focusing on active incidents. 

Add or remove watchers

The due date must be in the future.

This use case is valid for both conditions and validators . The only difference is that you can specify an additional error message when using a validator.

Compare two values condition

Compare two values validator

Require a fix version and add a comment.

This use case is valid for  validators.

Fields required or changed

(cog) 

When an issue is rejected, a comment will be added to the current issue mentioning the reporter.

Add comment

(cog) 

Execute remote action

(cog) 

toStringList()

getMatchingValue()

Create a sub-task for each selected component in the current issue.

Create issue

Require a non empty assignee.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Fields required

Fields required or changed

(cog) 

getNameFromAsset()

getAttributeFromAsset()

getAssetsFromAQL()

For the annual access review of applications used in the company and managed as Jira Service Management Assets, we want to create a dedicated task for each application owner to review the people who have access to the application they are responsible for. 

Create issue

(cog) 

Link your Epic each time you create a story.

Create issue

Check whether a Select List (cascading) field has a value in the transitioned issue.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

Make sure that an issue is not in an active sprint.

This use case is valid for both conditions and validators . The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

(cog) 

findPattern()

first()

Execute remote action

(cog) 

filterByStatus() subtasks()

Transition the parent issue to the "Open" status.

Transition issue

(cog) 

findReplaceAll()

Execute remote action

(cog) 

When an issue is identified as a bug, the functionality automatically adds all members of the support group as watchers. This ensures the support team is promptly informed about the bug, enabling them to communicate effectively with customers regarding any errors that occur on the customer side.

Add or remove watchers

Require a at least two attachments.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Compare two values condition

Compare two values validator

(cog) 

Create an issue in the current project and additionally set a summary.

This use case comes in handy if you quickly need to create i.e. a new bug which relates to the current issue

Create issue

(cog) 

Add a simple comment to an issue mentioning the reporter.

This use case might come in handy if you don't want to use extra events in your notification schemes to notify specific users - like the reporter.

Add comment

(cog) 

Update the  fix version  of all  sibling sub-tasks  from the  current issue .

Update linked issue or sub-task

(cog) 

epic()

issuesUnderEpic()

filterByStatus()

Copy the values of the fields defined in the Update fields post-function to the issues under the epic after their creation.

Update fields Transition issue

(cog) 

Execute remote action

(cog) 

jiraExpression()

Within the Send email post function you have the possibility to send HTML links in the message as well.
This use case shows an approach to send an email to the project lead linking the most recent attachment. 
It is normally applied after executing a transition, if an attachment was added there. This will then be linked to.

Send email

(cog) 

Create a sub-task and copy only relevant attachments using filename-based regex (e.g. ^final_.*)

Create issue

Check the number of times that a field has changed.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

Check whether the parent of the current issue is of a certain issue type.

This is particularly important if you want to reuse a workflow for multiple sub-task issue types but only want a transition to be available if the sub-task belongs to a certain user story or a bug.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

(cog) 

Execute remote action

(cog) 

dateTimeToString()

Set a Date Time Picker field to the current date

Update fields

Evaluate custom fields of different types with Jira expressions.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

Evaluate users and hide transitions based on the outcome.

This use case is valid for both conditions and validators . The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

(cog) 

Execute remote action

(cog) 

linkedIssues()

Automatically transition issue, if all linked issues are in specific status.

Transition issue

(cog) 

Automatically assign and issue to the project lead.

Issues will only be re-assigned if the priority of the issue is set to Highest to make sure that only important issues are being escalated.

Update fields

(cog) 

Execute remote action

Check whether the current issue has any unresolved sub-tasks.

This is particularly important if you want to block a parent issue as long as work is still being done on related sub-tasks.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Jira expression condition

Jira expression validator

(cog) 

Copy the  due date  value from the  current issue  to blocking  issues .

Update linked issue or sub-task

(cog) 

When an issue is created with the "Infrastructure" component selected, the priority will be set to "Highest".

Update fields

(cog) 

avg()

Automatically set issue priority during creation using the average of two custom fields. Since the field is only visible on the view screen, the automation must run as the App user to bypass editing restrictions.

Update fields

(cog) 

Each time a team member creates a new issue, the "Add or remove watchers" functionality automatically adds all colleagues from the onboarding team as watchers. This feature immediately informs the entire onboarding team about new issues, improving team coordination and support.

Add or remove watchers