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

Automation do not work for request participants.

szymon_szostak

Hi!

I am trying to set up very simple automation. We're getting mail to support mailbox with alias from the product:

product.support@company.com

Ticket is being created, Request participants are being set up properly according to alias after ticket creation but automation is not meeting the conditions.

Zrzut ekranu 2021-08-6 o 14.18.41.png

No idea why it's not meeting condition. Anyone can see something wrong here?

Accepted answers

All comments

Fabian Lim

Hi @szymon_szostak

For the value changes trigger, did you set the operations to be for creation?

Regards

Gaurav_0av1h6

Hello @szymon_szostak

Welcome to the Atlassian community!!

You have an interesting use case, one which I have never tried before. I sent an invite to the email id which was required to be confirmed and created the below rule which is working as expected.

I would suggest sending an invite to the mail id 'product.support@company.com' and then try.

Please accept the answer if this helps solve your query else respond and allow others to share input.

Request participant.JPG

szymon_szostak

Hi! Thanks for answering.

It is set for all types of operations, so I guess it should catch it. I can see in the logs that it's triggered properly, but conditions are not met.

Zrzut ekranu 2021-08-9 o 08.00.26.png

szymon_szostak

Hi! Thanks for answering.

I have added incoming mail with alias at first place. Looks like automation is triggered correctly, but somehow, it's showing that conditions are not met.

Zrzut ekranu 2021-08-9 o 09.34.00.png

Gaurav_0av1h6

Hello @szymon_szostak

This means that Jira is recognising the trigger properly but not the condition. I would suggest you test it with your id, which will help you identify the exact condition that needs to be configured.

Also, please confirm if you are able to see the alias in the drop while setting the condition. This is another indicator that it is working or not.

szymon_szostak

Hi, thanks for such quick response.

This is strange - I really think this is some kind of issue with order of things going on during the issue creation. When the mail comes, it creates a ticket and then it's adding the request participant. I believe it's somehow triggering it before it saves the participant.

I've done some test where I changed the trigger to work on update and I was changing the priority - it worked like a charm.

Daniel Ebers

Hi @szymon_szostak

if you like you could test the following rule.
No guarantees given but I could imagine a timing issue. Also, at least there should be a log afterwards telling what Jira sees for the "Request Participant" that time:

Regards,
Daniel

Henk van Drie

@szymon_szostak
This solution also solved our problem with the: "When: Issue created" trigger.
Looks like that "Request participants" is filled after the ticket creation.
"Re-fetch issue data" will fix this.
This is our Rule:

Halim men

Thank you @Daniel Ebers Re-fetch issue data solved my automation based on participants!

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-desk

automation

jira-service-management-cloud

jira-service-management