How do I send email notifications to Reporters when bulk importing issues?
Asked by Amy Chamberlain:

Hi there! I work on a Procurement team that leverages JSM for our approvals and contract negotiation process.

Using the data in our contract lifecycle management (CLM) system, on a monthly basis, we export expiring contracts, transform the data for Jira and then bulk import "Renewal" issues into our JSM project. This includes importing w/ a standard configuration file -\> bulk changing issue type + request type.

The issue is, Jira doesn't notify the "Reporters" we've identified when these issues are created. We can't create an automation for that specific request type since folks occasionally submit it on their own, for various reasons.

What's the best way to notify a reporter that a request has been bulk-imported on their behalf? Would the "Send email for this update" during the bulk change (second part of the process) suffice? Or is there a better automation I can setup for this?

Thx in advance!


Answers:
author: Cristian IONESCU
body: Hi Amy,

1.When you're bulk importing tickets, you can include a column titled **Labels** and add a value, such as **"CreatedfromCSV"**. This label will serve as a differentiator for the tickets created through the import versus those created by users.

To automate a notification process, you can set up an automation rule as follows:

1. **Trigger**: Issue is created.
2. **Condition** : Labels contain **"CreatedfromCSV"**.
3. **Action**: Send an email to the reporter.

2.Or you can use "Send email for this update".

comments: author: John Funk
body: Hi Cristian,

The import will not cause the Automation rule to fire. Otherwise there is no reason to add the label.

<https://jira.atlassian.com/browse/JRACLOUD-81955>


author: Amy Chamberlain
body: [@John Funk](/t5/user/viewprofilepage/user-id/7148) can you elaborate on why an import would not trigger the automation? The issue is still created with the label, isn't it?

Asking because I like [@Cristian IONESCU](/t5/user/viewprofilepage/user-id/5123296) 's approach since it also creates an auditable record of which issues were imported vs which are submitted by Reporters.  

Unless there is another way to identify this?


author: Bill Sheboy
body: Greetings!

That defect from September 2016 seems out of date as importing a CSV file to create issues does generate the issue-created event and will trigger an automation rule. I just tested to confirm this with both paths to import with a company-managed project rule:

1. Filter \> View All Issues \> ... \> Import Issues from CSV
2. System Admin \> External System Import \> CSV

Kind regards,  
Bill


author: Cristian IONESCU
body: Automation update:

1. **Trigger**: JQL schedule
2. **Condition** : Labels contain **"CreatedfromCSV"**.
3. **Action**: Send an email to the reporter.

This should catch only the tickets with label: **CreatedfromCSV**


author: John Funk
body: That's good to hear! Not sure when it got fixed, because a few weeks ago it was not triggering.


author: Amy Chamberlain
body: Ahhh great! We run the next import next week so I'll come back with an update.  

[@John Funk](/t5/user/viewprofilepage/user-id/7148) I think Jira pushed several import features \~4-6 weeks ago (i.e. they removed the import option from the create-issue screen), could have been then?

This is all super helpful - thanks so much, everyone!


author: John Funk
body: Hi Amy,

I would suggest you do a sample import with just a couple of issues. Check the box to send the email and see if the Reporter gets notified. But makes sure you use a different user for the Reporter than yourself so that it doesn't get caught by other rules.

Let us know how it goes!

comments: author: Amy Chamberlain
body: [@John Funk](/t5/user/viewprofilepage/user-id/7148) this would not be ideal because we have several approvers and stakeholders in our process and would be triggering false notifications to Executives, other teams, etc. which we don't want.


author: John Funk
body: Understood.


Tags: cloud

jira-service-management

jira-service-management-cloud