Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

'Only include issues that have changed...' checkbox in Manual Trigger

Iñigo Ruiz March 15, 2024

I am creating automations in Jira Cloud for a Business Project where there are only two types of issues: Epics and one type of child issue.

To avoid having to manually assign and set the due date of the child issues of an epic one by one to the same person and date, I have created a simple automation which copies the Assignee, Due Date and Reviewer fields from an Epic to the child Issues (Manual Trigger).

This is the rule:

image.png

It works if I execute it just after creating the Epic and its child issues, but when some of the child issues have been edited (e.g. have some of these fields filled) it does not work.

When looking at the audit log, it says "no action perform", no action is performed and it says to uncheck the 'only include issues that have changed...' but I cannot find this option in the Manual Trigger config.

image.png

Why does the rule not work in this case?

1 answer

1 accepted

3 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 15, 2024

Hello @Iñigo Ruiz 

Welcome to the Atlassian community.

Has the For Related Issues step always been set to Children, or has it ever been set to another option? Some of the other options for Related Issues do include that checkbox.

Screenshot 2024-03-15 at 12.52.11 PM.png

 

If it has been set to another type of related issue, are you sure the audit log entry you are viewing is from an execution while the Related Issues option in the rule was set to Children?

Iñigo Ruiz March 18, 2024

Hi @Trudy Claspill ,

Thanks for your answer.

It has always been set to Children! I have run the automation again now to make sure the audit log is the same, and it is:

Screenshot 2024-03-18 091146.png

I have also been testing with different issues/epics. I want it to run always, not depending on changes in the children issues and I am not able to achieve that.

Ste Wright
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 18, 2024

Hi @Iñigo Ruiz 

Change to Sub-tasks as the related issue type on the Branch. If the box is checked, uncheck it - then change back to Children.

Publish the rule and then test and see if that works :)

Ste

Like Iñigo Ruiz likes this
Iñigo Ruiz March 18, 2024

Hi @Ste Wright 

Thanks! That worked! :D

So weird that it remains checked although 'Branch rule / related issues' is set to Children!

Like Ste Wright likes this
Ste Wright
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 18, 2024

Weird platform quirk ;)

Glad it worked!

Ste

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