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 Not Triggered for All Issues Imported

Sage Lesko

Our team-managed project has a list of issues that are created monthly. As we work through them, eventually we receive a payment from manufacturers. We want to record these payments in Jira using an CSV upload.

I've created a new issue type that when imported via the CSV, links to an existing issue (Epic) and updates a custom field within the Epic.

I've been successful if I do a smaller amount of payments to upload, but the automation doesn't work completely when a larger amount of issues are uploaded. I've been testing uploading larger and larger number of rows, and interestingly enough, came across one test that had half of the issues link properly to the epics and updated the custom field, while the other half uploaded and link properly, but did not update the custom field on the epic.

This is my CSV file, where the first 3 issues highlighted in blue did not update the fields in the Epic:

This is the audit log of the automation. I've expanded one of each type of automation: one that was successful and one where "no actions were performed":

This is an epic that shows the linked issues and updated the Payment Amount custom field:

This one shows that it was linked successfully to the epic but the Payment Amount field was NOT updated:

Clicking on the imported issue the Payment Amount was uploaded successfully:

Accepted answers

Sage Lesko

Here's the solution I found:

1. To update the imported issue to a new status

2. Updating the related issue when the status is transitioned and checking the box for allowing other rule actions to trigger this rule.

Thank you everyone for all of your help!

All comments

Trudy P Claspill

Hello @Sage Lesko

When asking for help related to an Automation rule not working as you expect, it is necessary for us to see the rule to try to debug it. Please provide screen images showing the details of the rule.

Sage Lesko

Hi, here is the outline for the Automation:

Issue Created:

Issue Type Condition:

Branch rules for Linked Issues:

Then Edit Issue:

Sage Lesko

Hi, I answered above instead of replying but here is the outline for the Automation:

Issue Created:

Issue Type Condition:

Branch rules for Linked Issues:

Then Edit Issue:

Trudy P Claspill

How is the link created between the newly created issue and the Epic?

If that is part of the CSV upload it is likely that the issue creation action is completed before the Link is created, and the Link doesn't exist at the time when the rule is run.

Try adding a Re-fetch action between the Condition and the For branch. That will slow down the rule a tiny bit and perhaps allow enough time for the Link to be created before the For branch runs.