Forums

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

Jira Automation not Triggering multiple value adds

oliver_jackson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 24, 2025

Hi,

I have an automation rule that is triggering value changed for a list of fields. Labels is one example but its a custom field.

The automation is only triggering for the last one if a user adds multiple at the same time.

For example, if user adds ComponentA, ComponentB, ComponentC the expected outcome would be to trigger the automation 3 times for each component.

The automation only triggers for ComponentC.

Has anyone experienced a similar issue?

2 answers

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 24, 2025

Hi @oliver_jackson -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

  • what type of project is this: company-managed, team-managed, JPD, etc.
  • an image of your complete automation rule in a single image for continuity
  • images of any relevant actions / conditions / branches
  • an image of the audit log details showing the rule execution
  • explain what is not working as expected and why you believe that to be the case

Until we see those...

 

Normally, field change triggers happen after the field changes.  And so for list fields such as Labels, Components, etc. the person needs to leave the field for the change to be detected.

For many list fields, the workaround for your scenario to manage just the additions would be to use the field change smart values for the additions, perhaps just processing those in the rule: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange--

Please note well: this will not work for all list fields because there are known defects with the changelog information supplied to rules for fields like Fix Versions, Affects Versions, and Sprint.  To detect only the additions for those, sometimes the changelog entries must be gathered using the REST API endpoint and manually parsed in the rule logic.

 

Kind regards,
Bill

0 votes
oliver_jackson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 24, 2025

So managed to solve this but now I need to remove a link based on this component.

For every component
  For every link
    if link contains component in summary
    send web request


Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events