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; } } }

Can JIRA email users specific tasks when an issue is created?

Brad Beaver

New to JIRA here. Just days away from going live.

We would like to ability to automatically email users specific tasks (or sub-tasks) when a certain issue is created.

For example, when a new customer comes onboard.

1. Create Issue under the "New Customer" project and use the "New Customer" Issue Type.

2. Email gets sent to: Employee-A to create a new system account, Employee-B to send them documentation, Employee-C to provide them with their product, etc....

I've been trying to get my head around the Notification Schemes and Issue Type Schemes but I'm just not having any luck. I did stumble upon the built-in scripts just a moment ago which might seem like they can help but could be a bit over my head right now.

Does anyone out there do this with their setup?

Accepted answers

Hugh Prior

A relatively easy way would be to define a workflow which simply puts the required actions in a sequence.

e.g. define a workflow which has status:

"Waiting for new account to be created". This would have a transition "Account creation done" which would change the status to:
"Waiting for documentation to be sent" and automatically change the assigned person to person B. This would have a transition "Documentation sent" which would lead to a status called:
"Provide them with product" and automatically change the assigned person to person C.

It doesn't give the parallelism which you are thinking of, but if each person does their job efficiently it might be fine and would keep things simple.

All comments

JamieA

You can do anything with plugins or scripting, but perhaps it's not something you want to get involved in with being just a few days from going live.

Rather than sending emails to A, B and C when a "New Customer" issue is created, I think you'd be better off having jira automagically create three subtasks under the new customer issue, corresponding to the various onboarding things you need to do. If they are assigned to A, B and C then jira will send them mails.

If you have a built-in scripts link then maybe you have the script runner plugin installed. On the post-functions of the create step you can have three post-functions which will create a sub-task.

If you want to stick with plan A you can have jira mail the three people, but it's a hassle to get jira to send email with different content to the 3 people.

Sergey Papurin

You can use jython or groovy script post function after create transition

192.168.0.1 - ip of jira deafult SMTP server

Jython code:

sender = 'your.jira@default.email'
to = 'user1@email.com'
subj = "SUBJECT1"
body = "MESSAGE BODY1"

server = '192.168.0.1'

from email.MIMEText import MIMEText
msg = MIMEText(body, 'plain', 'utf-8')
msg['Subject'] = subj
msg['To'] = to
msg['Importance'] = 'high'

import smtplib
s = smtplib.SMTP(server)

s.sendmail(sender, [to], msg.as_string())
s.quit()

Hugh Prior

A relatively easy way would be to define a workflow which simply puts the required actions in a sequence.

e.g. define a workflow which has status:

"Waiting for new account to be created". This would have a transition "Account creation done" which would change the status to:
"Waiting for documentation to be sent" and automatically change the assigned person to person B. This would have a transition "Documentation sent" which would lead to a status called:
"Provide them with product" and automatically change the assigned person to person C.

It doesn't give the parallelism which you are thinking of, but if each person does their job efficiently it might be fine and would keep things simple.