Add Service Desk customer (Cloud only)

Add new customers to your Jira Service Desk project with this handy little action. You can use smart-values in all fields and add the customer to one of your existing organizations

Smart fields: Email, Name, Organization
Available in Server Lite: No


Add Watchers Action

Sometimes you just want to make sure that certain people get notified when an issue is updated. With this action you can add as many watchers as necessary!


Screen Shot 2016-09-13 at 2.14.41 PM.png

Assign Issue Action

For when you want to change the assignee of an issue. You can also change the issue to unassigned.


Screen Shot 2016-09-13 at 3.03.08 PM.png

Clone Issue Action

Copies an issue into a specified project and issue type. You can also add and remove fields using the advanced section. E.g. add a label or version.


Add Comment Action

Add a comment to the active issue. You can reference the active issue's fields to personalise the message.


Create Issue Action

Create an issue of specified type in a specified project. For simple issues you can just use the provided fields. For more advanced use cases, you can specify any field using the Advanced field.


Create Service Desk request (Cloud only)

Creates a new Jira Service Desk request. Just like the 'Create issue' action, this action allows you to configure any field available using smart-values.


Create sub-tasks action

A quick way to add those common tasks.

For more complex issues you will need to use the create issue action.
Smart fields: Summary
Available in Server Lite: No

 


Delete attachments Action

Use this action to clean up old attachments using regular expression matches based on the attachment filename!

Smart fields: Regular Expression
Available in Server Lite: Yes


Delete issue action

Sometimes you just need to get rid of some pesky issues automatically!


Edit Issue Action

You can easily edit the active issue using this action. For more advanced edits, you can set and update fields using the Advanced field.


Link any two issues in Jira with this handy little action. You can select a link type and use the trigger issue, smart-value or simply an issue key to link to.


Add Log Message Action

Sometimes you need to debug actions or just record that something was done. Use log messages to add a message to the audit log.


Publish event (Server only)

An advanced action to allow you to publish Jira events (system or custom) that other add-ons and integrations can listen for.


Find related issues for the issue that triggered the rule such as sub-tasks or stories in an Epic. This component will then allow you to create a parallel rule chain that will execute just for these related issues!

Smart fields: Supported in all actions & conditions in the parallel rule chain.  Special value is {{triggerIssue}} to access the issue that triggered the original rule
Available in Server Lite: No


Send Email Action

Sending emails is still a crucial part of most teams processes. This action allows you to automatically send an email. Using Smart Fields you can customise/personalise it.


Send HipChat Notification Action

Notify a HipChat room when the rule is run. You can customise/personalise the message using the active issues fields.


Send Slack Notification Action

Notify a team or an individual when the rule is run. You can customise/personalise the message using the active issues fields.


Send Twilio Notification Action

A lot of service teams rely on SMS for on-call scenarios. With this action you can send a notification using the Twilio service. You will need to have an account already set up.


Send Webhook Action

Quite often you need to integrate with other systems. Webhooks are becoming a common way for applications to talk. This action allows you send an out bound Webhook to notify another system when this rule is run. You can also include the issue in the request.


Transition Issue Action

This rule transitions an issue through a workflow. You can specify fields to update and add comments using the Advanced field.


Field value changed trigger

Use this trigger to run an automation rule whenever a given field's value changes. Want to know when an issue's priority changed to Critical? Use this trigger with a compare condition!


Incoming Webhook Trigger

Quite often you need to integrate with other systems. Webhooks are becoming a common way for applications to talk. The trigger listens for a Webhook request and triggers a rule when it receives one. You can pass in a data to reference in later components or run a JQL to retrieve issues.


Issue Assigned Trigger

Rule is run when an issue is assigned to a user. The trigger needs no configuration.


Issue Commented Trigger

Rule is run when a comment is added to an issue. The trigger needs no configuration.


Issue Created Trigger

Rule is run when an issue is created. The trigger needs no configuration.


Issue Deleted Trigger

Rule is run when an issue is deleted. The trigger needs no configuration.


Issue Moved Trigger

Rule is run when an issue is moved to the specified project.


Issue Property updated (Server only)

This advanced trigger allows you to react to issue property changes in Jira Server. You can listen to changes for specific properies or all properties.


Issue Transitioned Trigger

Rule is run when an issue is transitioned through its workflow. The trigger needs no configuration.


Issue Updated Trigger

Rule is run when an issue is updated/edited. The trigger needs no configuration.


Manual Trigger

This rule adds a panel to the view issue page that allows you to manually kick-off a rule. This is great for common tasks. You can restrict who can run/see this rule.


Multiple issue events trigger

Sometimes you may want to trigger the same rule when a number of different events occur. For example you may want to add the user that updated an issue to a custom field when an issue is updated, transitioned or assigned.


Scheduled Trigger

This executes a rule on the specified schedule. You can run the rule on a defined period or use a Cron expression for more complex schedules. You can choose to either run a JQL query or simply run the rule if you're trying to create issues on a schedule.


Compare Condition

This powerful condition allows you to compare objects using Smart Fields and Regular Expressions.

Smart fields: First value, Second value
Available in Server Lite: No


Issue Attachments Condition

Allows you to check whether a field has any attachments or not.


JQL Condition

This condition checks to see if the issue matches the specified JQL


User Condition

Allows you check a specified user exists or is in a specified group.


This condition can interate over a number of related issues and check, if all, some or none match a given JQL query.