Automation Trigger "When: Issue Updated" not Firing

Kyle Pontis October 16, 2024

I have a very simple automation set up that is supposed to update all sub-tasks on an issue to fill out a custom field from the parent issue.

 

The workflow is only 2 steps. 

When: Issue Updated

Then: Edit Issue Fields

 

The when trigger does not seem like it can be customized in any way. The Edit issue fields step simply has the selected custom field I made selected, and the action is to "copy from parent".

 

Seems simple enough. However, try as I might I cannot get the automation to fire. I have tried commenting on the sub task, I've tried changing its status, and its assignee. Nothing seems to trigger the automation to even attempt to fire.

 

We do have a security screen enabled for this project but I have ensured that the automation "user" is allowed to access all issues. Can anyone help me determine why this automation is not firing, much less working?

3 answers

1 accepted

2 votes
Answer accepted
Kyle Pontis October 16, 2024

I was able to solve the issue via using a different trigger as well as a branching task:

Trigger: Field Value Changed (I selected my custom Participants field)

Branch

   For: Subtasks

Then: Edit Issue Fields (Sets the Participants field, copied from Parent issue)

 

This effectively does exactly what I wanted it to. Thanks very much to @Aaron Pavez _ServiceRocket_  for the assistance!

0 votes
Kyle Pontis October 16, 2024

Hi Aaron,

Thanks for your help. I have attached images of the automation and its rules. Let me know what you think!Screenshot 2024-10-16 at 1.18.23 PM.pngScreenshot 2024-10-16 at 1.19.37 PM.png

0 votes
Aaron Pavez _ServiceRocket_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 16, 2024

Hi @Kyle Pontis 

Can you share a screenshot of the whole automation, please?

Any errors in the audit logs? a screenshot will help us too.

I just created a similar automation and the subtask gets the value from the parent.

Maybe permissions? who is the actor of the automation? is it Jira automation?

Regards

Aaron

 

 

Kyle Pontis October 16, 2024

Sorry, I should have replied to your specific comment. I did reply on the main post however!

Kyle Pontis October 16, 2024

The automation is not even firing, so there is nothing in the audit log to present, unfortunately.

 

Jira automation is indeed set as the actor.

Kyle Pontis October 16, 2024

I have tried adjusting the automation so that the actor is me, still no luck.

Aaron Pavez _ServiceRocket_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 16, 2024

HI @Kyle Pontis 

What type of field is participants?

A custom field? a third party field custom field(coming form an app?)

Is the field available in the sub task? added to the screens create/edit?

Can you test this with another field?

Select the assignee for example. or a text field will do. Lets see if the automation runs then.

2024-10-16 16_35_04-Audit log - Automation - CaseSF - Jira — Mozilla Firefox.jpg

Regards

Kyle Pontis October 16, 2024

Hi @Aaron Pavez _ServiceRocket_ 

The "participants" field is a custom field that I created (a user picker field). The purpose of the field is that if you enter a person into said field, it allows them to see and comment upon the issue. This is to allow collaborators to access certain issues, but prevent them from perusing the rest of the project board.

So now what I am attempting to do, is to have the sub-issues automatically include the participants that are listed in the parent issue. I was hoping this would be a default type of thing but it doesn't seem to be. So this is where the automation comes in.

The field is available for all issues/types, as I have added it to the scheme/screen that we are using for this board.

Good idea about attempting to use a different field to test with. I will try that and get back to you!

Kyle Pontis October 16, 2024

I have attempted to change the field being updated from Participants to Asignee. Unfortunately, after placing a comment on the sub-task for make it update, no automation was triggered still.

Aaron Pavez _ServiceRocket_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 16, 2024

Hi @Kyle Pontis 

A comment is not an edit. You need to change a field in the sub-task to trigger the automation.

Regards

 

Aaron Pavez _ServiceRocket_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 16, 2024

One thing about this automation. I would add a validator like if the issue type is sub task to avoid running the automation all the time. As is, it will run for all edits and that will use the automation quota fast.

Regards

Kyle Pontis October 16, 2024

Oh definitely. I am just trying to get the automation to fire at this point, and then add onto the complexity.

 

In any case I have changed the automation so that whenever an issue field (participants) is updated, send me a Slack post. 

 

This automation IS working, so I guess the issue previously has to do with getting the "Issue Updated" trigger to properly fire.

Perhaps it would be easier to user the issue field update trigger instead since I know it works? 

Aaron Pavez _ServiceRocket_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 16, 2024

Hi @Kyle Pontis 

That will surely help. The first automation will run when you EDIT any field. The comment won't work.

Now that you know this automation runs when the PARTICIPANTS changes, it will fire for sure.

Regards

Aaron

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events