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; } } }

Jira Automation intermittently fails to update a custom field

gollapudi sidhvi

Hi Atlassian Community,

I have a JSM Cloud automation rule that updates a Created Month custom field. The rule actor is Automation for Jira, and the field context is correctly configured.

The automation works successfully for most tickets, but intermittently fails for some tickets with the following errors:

“Issue doesn't exist or you don't have permission to see it”

and

“Edited issue successfully, however some of the set fields aren't available. Fields ignored: Created Month”

The field is intentionally not added to the View/Edit screens as it is used only for background processing and dashboards.

What could cause this intermittent behavior for only some tickets, while the same automation works successfully for most tickets?

Accepted answers

All comments

Nikola Perisic

Hello @gollapudi sidhvi

In your Jira space and Browse projects permission, Automation for Jira user needs to be added in order to see the work item, check your scheme.

gollapudi sidhvi

Hi @Nikola Perisic

Thanks for the suggestion. We have already verified that atlassian-addons-project-access is included in the Browse Projects permission for the project

The issue is also intermittent — the same automation successfully edits most work items but fails for only some of them. In some cases, the audit log shows “Issue doesn't exist or you don't have permission to see it”, while in others the issue is edited successfully but the Created Month field is ignored.

Could there be any other permission, issue security, or Jira Cloud limitation that could cause this behavior for specific work items even when atlassian-addons-project-access has Browse Projects permission?

Nikola Perisic

@gollapudi sidhvi

Not the atlassian-addons-project-access - this role is being used by Atlassian marketplace application. In browse projects permission, you have the option to update it by adding a single user which is Automation for Jira.

gollapudi sidhvi

Thanks for clarifying. We can add the Automation for Jira user directly to Browse Projects. However, will this also resolve the “Edited issue successfully, however some of the set fields aren't available” / “No fields or field values to edit” error?

We are seeing both errors intermittently, so I’d like to confirm before making the change in live environment.

There are two different failures here, so I would diagnose them separately.

For the ignored Created Month field, its absence from the relevant Edit screen is important: a valid field context alone isn’t sufficient. Atlassian documents this exact automation error and lists missing Edit-screen fields as a cause:
https://support.atlassian.com/jira/kb/some-of-the-set-fields-arent-available-error-in-jira-cloud-automation/

In a test project, add it to the Edit screen used by a failing work-item type and rerun the same action.

For the access error, compare one successful and one failed item: project/type, security level, status, and the actor’s Edit permission—not only Browse. Check for workflow properties restricting edits. Keep the original security restrictions intact while identifying the difference.

If the failures occur immediately after creation, capture that timing and the full action sequence too.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

custom-field

jira

cloud

dashboard

automation

field-configuration

context

jira-service-management-cloud

jira-service-management

screens