automation failed with error

[黃惠婷]

Hi, 

I just created an automation rule to update the due date and assignee.
But complete with some errors. This rule action is "Automation for jira". 

The error message below: 

• Edited work item successfully; however, some set fields aren't available. Fields ignored: Due date (duedate)
• Unable to assign work items VMRT-7: (You do not have permission to assign issues.)

I just checked the project permission, "atlassian-addons-project-access" is included in the scheduled and edit issues. 

Is there any configuration I should check? 

Thanks, 

March 

[Christos Markoulatos]

Hey @黃惠婷 welcome

The errors mean two separate things:

1. Due date ignored – The field isn’t available on the issue’s screen or request type.
   → Check Project Settings → Screens and make sure Due date is on the Edit/View screen for that issue type. If it’s a JSM request type, add Due date to the form.

2. No permission to assign – The automation actor needs Assign Issues permission.
   → Go to Project Settings → Permissions → Assign Issues and add atlassian-addons-project-access (or the user the rule runs as).

After updating both, re-run the rule.
If you want to avoid errors when fields are missing, add a “Field value exists” condition before the edit action.

Hope this helps!

[Bill Sheboy]

Hi @黃惠婷 -- Welcome to the Atlassian Community!

The most likely cause of that symptom is a known, racetrack timing problem with the Work Item Created trigger (and others).

What happens is the rule starts before all of the data is available, leading to unexpected behavior, permission errors, and sometimes even a work item without a type!  Atlassian knows about this defect and is working on architectural changes to fix it.

Until that is fixed, the mitigations are:

• Immediately after that trigger, add the Re-fetch Work Item action.  This will slow the rule slightly, reloading the data before the steps proceed.
• And, do not use the new feature to add conditions directly to the trigger.  As the data may not be present when the rule starts, the conditions may not work as expected.  Instead, add separate conditions after the re-fetch action described above.

Please try adding that action and re-testing your rule.  Thanks!

Kind regards,
Bill