nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How Customize Email Notififcation base on Issue type?

Shah Baloch

I created a new issue type "Email" and set up the mail handler. When a customers report an issue via email, it'll create a ticket using the "Email" issue type. Since reporters have accounts and they get emails from Jira about issue creation. I would like to have customized email notification. for example:

"Hi Reporter,
Thank you for reporting the issue, your ticket number is XYZ-250. We'll get back to you as soon as possible".

How can I make it work just for one issue type. That service desk has other issue types, we just want to use a different issue type for emails for tracking purposes.

Thanks

Accepted answers

All comments

JimmyVanAU

Hi Shah,

Unfortunately there's no simple way with out of the box functionality to change how email works. It's either on or off.

If you have other marketplace apps, then you may be in luck. Firstly, there are dedicated email apps which are fairly easy to use - Email This Issue, Jira Enterprise Mail Handler, are the two biggest ones. They allow you to tailor emails however you like as that's their primary purpose.

If you don't have a dedicate mail app, many instances have ScriptRunner (or any scripting tool) or Automation for Jira for other purposes. These tools can be set up to respond to events, such as issue creation of a particular issue type, to send a customised email.

Hope that helps,
- Jimmy

Boris Berenberg - Atlas Authority

We support this type of configuration in Notification Assistant for Jira

SWAPNIL SRIVASTAV

Hello @Shah Baloch ,

This can be done via plugins- "Script Runner for JIRA" and "Jira Workflow Toolbox".

Shah Baloch

I already have Script Runner installed. How I can make it work? Thanks

Daniel Ebers

Hi @Shah Baloch

using Script Runner I would suggest you edit the existing workflow, there especially the "Create" transition and put a new post function "Send a custom email" in it.

Under "Condition and Configuration" can you narrow it down to a specific issue type.
After that you need to type in something for the "Email" and "Subject" template - basically the info you want the reporter to get back after they create an issue.

Something like:
Email template:
"Request $issue.issueType.name $issue.key created with success."
Subject template:
"Request $issue created"

Be sure to select "Reporter" in "To issue fields".

All other settings according to your requirements if any.

When saved and the workflow was published your Reporter will get an email when raising a request of defined issue type according to the settings in post function.

Regards,
Daniel

Shah Baloch

Thank you I can give it a shot. Will the user still get the actual notification with issue details? I mean whenever users create an issue Jira will send them an issue-created notification. How I can stop that actual notification so the user can the custom email?

Thanks

Daniel Ebers

If I understand you right and assuming this is a Jira Service Management project you would have to adjust the Customer Notifications:
https://confluence.atlassian.com/servicemanagementserver/managing-service-project-notifications-939926348.html

However, this would affect all Issue Types.

For a Jira Software/Core project you would have to inspect the Notification Scheme:
https://confluence.atlassian.com/servicemanagementserver/managing-service-project-notifications-939926348.html

The content of the email sent through post function in workflow can be adapted and adjusted according to your needs. Directly on the configuration page you can see an example for some variables you can use there.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-software

mail-handler

notification

jira-server

issue-type

jira-service-management

jira-service-management-server