How to Trigger Emails and Notifications from Jira Service Management Customer Forms (2026)

Lead

Set up JSM Forms to automatically send branded customer emails, collect structured data, and trigger agent notifications without manual intervention. When a ticket moves to "Awaiting Customer Info," an automation rule sends a form link; the customer fills it out; data lands on the ticket; the agent gets notified. Verified against Atlassian Cloud Jira Service Management Forms on 2026-05-05.

Prerequisites

How ScaleIT handles this: See Jira Rescue

• Jira Service Management Cloud project with admin access
• Permission to create and edit forms (Project settings → Forms)
• Permission to create automation rules (Project settings → Automation)
• Custom fields created for form data (optional but recommended)
• SMTP or configured email delivery for your Atlassian instance

Steps

Creating the Customer Form

1. Navigate to your service project and select Project settings → Forms.
2. Click Create form and give it a clear, action-oriented name (e.g., "Customer Information Request").
3. Add form fields one at a time using the Add field button.

• Keep the form to 5–8 fields maximum to prevent abandonment.
• Use required toggle for fields customers must answer; leave nice-to-haves optional.

1. For each field, click the field and select Link to Jira field to map the form data to a custom field on the issue.
2. (Optional) Use Show/hide rules to enable conditional logic: if a customer selects "Hardware issue," show only hardware-related fields.
3. Click Publish to make the form available.

Setting Up the Trigger Automation Rule

1. Navigate to Project settings → Automation → Rules (or Create rule).
2. Set the trigger to When → Issue field changed → select Status → choose the status that should prompt the form (e.g., "Awaiting Customer Info").
3. Click Then and add the action Send email.
4. In the email template:

• Subject: Include the issue key for clarity (e.g., [{{issue.key}}] We need a few details from you).
• Body: Write a brief explanation of why you're asking and what happens next.
• Form link: Include the form URL. The standard format is:

      {{baseUrl}}/servicedesk/customer/portal/{{portalId}}/{{issue.key}}/forms/{{formId}}

This drops the customer directly into their specific form.

• Recipient: Set to Reporter so the customer receives the email.

1. Click Save to activate the rule.

Setting Up the Form Submission Automation Rule

1. Return to Project settings → Automation → Rules and click Create rule.
2. Set the trigger to When → Form submitted.
3. (Optional) Add a condition: Issue status → equals "Awaiting Customer Info" (prevents firing on forms submitted at other stages).
4. Click Then and add the first action: Transition issue → select the next status (e.g., "In Progress").
5. Click Then again and add a second action: Send email (or Send notification).

• Recipient: Set to Assignee.
• Subject: e.g., [{{issue.key}}] Customer information submitted.
• Body: Include a summary of what was submitted and a link to the ticket.

1. Click Save.

(Optional) Customize Email Templates

1. Navigate to Project settings → Notifications → Email templates (if available in your JSM version).
2. Edit the Default template to add your company logo, colors, and brand voice to all outbound emails.
3. Use smart values to personalize greetings: {{issue.reporter.displayName}} or fall back to "Hi there" if the name is unavailable.

Verify

• Create a test ticket via the portal and transition it to "Awaiting Customer Info" as an agent. Confirm the email arrives in your inbox within 1–2 minutes.
• Open the form link from the email and submit test data. Verify the data appears in the correct custom fields on the ticket.
• Confirm the ticket auto-transitions to the next status after form submission.
• Confirm the assignee receives a notification that the form was submitted.

Troubleshooting

Form link in email doesn't work or shows 404

• Cause: Incorrect portal ID or form ID in the template URL, or the form was moved/deleted after the rule was created.
• Fix: Navigate to Project settings → Forms, click the form, and copy the form ID from the URL bar. Re-check the portal ID in Project settings → Portal. Update the automation rule with the correct IDs.

Email goes to spam or customer doesn't receive it

• Cause: Missing or misconfigured SPF/DKIM records at the account level, or the customer's email domain is filtering Atlassian mail.
• Fix: Contact your Atlassian admin to verify SPF and DKIM records are set up for your instance. Ask the customer to check spam/junk folders. Consider using a branded sender name instead of a generic one.

Automation rule doesn't fire after status transition

• Cause: The rule is disabled, the status name doesn't match exactly, or the reporter isn't a valid email contact.
• Fix: Navigate to Project settings → Automation → Audit log to see where the rule stopped. Verify the status name matches exactly (including case and spacing). Confirm the reporter has an email address in their Atlassian account.

Form data doesn't map to the Jira field

• Cause: The form field isn't linked to a Jira field, or the field type doesn't match (e.g., text form field linked to a number custom field).
• Fix: Return to the form editor, click the field, and ensure Link to Jira field is set to the correct custom field. If using a picker field (Assets or object), ensure the custom field type supports objects.

Customer receives multiple emails or notification batches are delayed

• Cause: Duplicate automation rules, or notification batching is enabled in your project.
• Fix: Check Automation → Rules to ensure only one trigger-email rule exists. Navigate to Project settings → Notifications → Notification batching and set batch window to Immediate if you need real-time alerts.

Smart values (like {{issue.reporter.displayName}}) show an email address instead of a name

• Cause: The customer was added via email without setting a display name in their Atlassian account.
• Fix: Use a conditional smart value: {{#issue.reporter.displayName}}Hi {{issue.reporter.displayName}}{{/issue.reporter.displayName}}{{^issue.reporter.displayName}}Hi there{{/issue.reporter.displayName}} to fall back gracefully.

CTA

Do you want your service desk to run on autopilot, but setting up automation feels like the hard part? ScaleIt builds end-to-end form workflows, automation rules, and notification templates for JSM and we handle the configuration so you don't have to. Let us know if you'd like help setting this up for your team.