Send one single email when issue is updated by reporter

[Tschilar, Stacey]

I'm trying to create an email notification that will get sent to my team when the reporter makes changes to their issue. It's working except it's sending an email for every field that gets changed...  I really just want one email saying changes have been made. I tried putting in a delay but no dice. It just delays both emails by 20 seconds! 

 

[Trudy Claspill]

Hello @Tschilar, Stacey 

The rule will be triggered by each update to the issue. Each field that gets changed is a separate update.

What problem are you trying to solve by creating this automation rule?

Is it not sufficient to rely on the Notifications configuration for the project to send notifications to interested parties when the issue is updated?

[Tschilar, Stacey]

The issue is created via a front door process, where the reporter is the person filling out the form. We want the team to know if the reporter, specifically, has changed anything about their issue since they submitted it. Right now changes are happening without the team working the issue being notified, and we don't necessarily want all notifications turned on for any person working it. If that makes sense! 

[Trudy Claspill]

Thank you for that additional information.

With just native Jira functionality you there is not a "good" way to accomplish what you want. There are some possible work-arounds. Here is my thought process:

1. The rule will be triggered for every update the Reporter makes, so each update would result in an email being sent.

2. If you want to send an email after only the "last" update, then you need to record when the last update was made. But you never really know when the Reporter is done making updates.

3. So, you could use a custom field and this rule to record a timestamp for the last time the Reporter made an update. The timestamp field would be updated each time the Reporter makes an update.

4. And you could add another scheduled rule to run periodically throughout the day to look at that timestamp field. If the value is some specified period of time in the past, then send the email and clear the field.

You could, for instance, run the schedule rule hourly and check if the timestamp field is an hour or more in the past.

Clearing the field is necessary so that you can "restart" the tracking of updates by the Reporter to determine if another email is necessary when another hour has passed.

[Tschilar, Stacey]

wow, well...  I'm following your logic but, a little discouraged with the amount of workarounds lol.

I got some feedback that we're only interested in changes to 3 fields (description, comments, priority) so if I can get that to work, I might just roll with the possibility of 3 email notifications.

Thank you for taking a look!