• Products
  • Get started
  • Documentation
  • Resources

Jira Automation docs have moved

All content related to Jira Cloud Automation, previously under the Automate your Jira processes and workflows section, have moved to the new Cloud Automation docs.

Go to Cloud Automation documentation | Why did we do this?

Create and edit the content of your customer notifications

You must be a project administrator to create or edit customer notifications.

Notification templates can’t be edited if you are on a Free plan of Jira Service Management.

To access the feature, upgrade your plan and complete the evaluation period. If you need to enable the feature during your evaluation period, contact Atlassian support.

To create or edit notifications:

  1. From your service project’s sidebar on the left, go to Project settings () >Customer notifications.

  2. Choose the notification you want to edit, then select Edit.

  3. Choose recipients by selecting and editing To. You can delete recipients by selecting the X next to an added recipient.

  4. Under Content, edit the message. You can add variables using the Insert variable drop-down to pull blocks of information from issues.

  5. Toggle Enable to turn customer notifications on or off.

  6. Select Save to confirm your changes.

Choose recipients

When choosing recipients, add at least one of the following to the To field:

Reporter (customer)

The reporter of the request.

This notification is sent even if the reporter has opted out of receiving notifications on the portal.

Customers involved

All customers involved in the request, including the reporter and request participants.

This notification is not sent to customers if they have turned off notifications for an individual request in the portal or a request's email thread.

Added participants

The people who have been added as request participants.

Added organizations

The people in an organization that the request has been shared with.


The agents who need to approve or decline a request.

Exclude person who caused the action

Prevents the person who triggered the rule from receiving a notification. For example, if a customer adds a comment to a request, you can choose to exclude them so they don't receive a notification about their own comment.

Include issue variables

Data stored in the following variables will be hidden from notification emails when a compliance setting is enabled by your site admins. Your customers will need to log in to the portal to view the full content of a request.

  • Issue summary

  • Issue description

  • Comment

  • Attachment

Learn more about the compliance settings

You can use variables to pull blocks of information from issues and insert them into your message. Select the Insert variable drop-down menu to add valid variables for the notification you're customizing.

Recipient name

The full name of the person receiving the email. ${recipient.name}

Name of the person who caused the action

The full name of the person who triggered the notification, for example by adding a comment. ${event.user.name}

Issue summary

The summary of the issue, or blank if there's none. ${issue.summary}

Issue description

The description of the issue, or blank if there's none. ${issue.description}

Issue key

The issue key (for example, IT-123). ${issue.key}

Issue reporter

The full name of the user that reported the issue. ${issue.reporter.name}

Issue resolution

The resolution of the issue, for example "done". ${issue.resolution}

Request URL

The URL of the request in the portal. ${request.url}


The comment added to the issue. This is only available using the "Comment added" or "Comment edited" WHEN trigger. ${comment}

Request status

The customer-visible status of the request, as shown in the portal. ${request.status}

Portal name

The portal name, which can be edited on the Portal settings page. ${portal.name}

This page is for company-managed projects

If the lower-left of your service project sidebar says you're in a team-managed project, check out these team-managed project articles instead.

Learn more about the difference between company-managed and team-managed projects.


Additional Help