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

Request Participants - how to only email newly added participants?

Tyler Myalls

I'm running an automation to send an email to "Request Participants", but only want the email to be sent to new participants.

If I add someone, then they get an email, but if I add another person at a later date/time, the initial participant gets another email as well.

Any thoughts on how to only send the newly added "Participant" an email?

Accepted answers

Marc -Devoteam-

Hi @Tyler Myalls

The default notification rule does this, based on a participant added. I suspect you have disabled this..

So (hypothetically), you would to have the need to 1st find the new participant added.

In my opinion this could only be found using the API to get the issues changelog, this will provide a dat and the display name of the user.

Then you would need to store this information and then use this information to find the users email address.

Use this response a smart value in to to field of the mail action.

So you need to use web requests to different API endpoints and use the response for a request to be used in a variable for a follow up request.

All comments

Marc -Devoteam-

Hi @Tyler Myalls

The default notification rule does this, based on a participant added. I suspect you have disabled this..

So (hypothetically), you would to have the need to 1st find the new participant added.

In my opinion this could only be found using the API to get the issues changelog, this will provide a dat and the display name of the user.

Then you would need to store this information and then use this information to find the users email address.

Use this response a smart value in to to field of the mail action.

So you need to use web requests to different API endpoints and use the response for a request to be used in a variable for a follow up request.

Bill Sheboy

Hi @Tyler Myalls

Without seeing the details of your automation rule...if the trigger is Field Value Changed for the Request Participant, you could try using the field change smart value for the added values only:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange--

A couple of things to note for using this approach:

When a multiple-selection / list field changes too often, the changelog smart values may not work be accurate in rules. The only workaround I know for that is to explicitly read the changelog entries using the REST API endpoint and parse them in the rule.
The fieldchange smart values can only return one value, and thus if multiple values changed one must manually determine the added values using some complicated logic, created variables, and the changelog smart value with iteration.

Kind regards,
Bill

Tyler Myalls

@Marc -Devoteam- you are correct - it was disabled, which is odd since I'm the only admin of this particular project and it was enabled last week.

Marc -Devoteam-

Hi @Tyler Myalls

A Jira admin, product admin or org admin can access these settings as well.

they don't need to be specified on the project in the admin role, as there permissions are on a higher level.

They can access any projects project settings, without being mentioned on the project itself.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management