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 Rule "Could not find your configured field, it may have been deleted?"

Jonathan Domanus

I'm working on locking down permissions to our project. I have removed all default permissions, and planning to issue permissions on an as-needed basis for individuals to perform the duties of their role.

A nasty side-effect of this is that my Automation rules are now failing.

I have a form on the Jira Service Desk side that someone submits and we then ticket off the creation of about 20 other tickets. The Service Desk project has the rule, and it creates the tickets in another project. The 2nd project is what I'm trying to lock down.

I'm receiving an error on the "Create Issue" step as outlined below:

Create issue

Could not find your configured field, it may have been deleted?

Policy Name, Policy URL

Error creating issue

Policy Name is required. (customfield_10098), Policy URL is required. (customfield_10099)

Does anyone know what the proper permissions needed would be to support this scenario? Thanks in advance!

Accepted answers

John Funk

Hi Jonathan,

You need to make sure that the atlassian-addons-project-access user has access to pretty much everything. Otherwise all of your add-ons will fail.

All comments

Bill Sheboy

Hi @Jonathan Domanus

I believe that is the "Create Issues" permission.

Have you considered changing your rule actor (user) to be one with the permissions needed for the rule to work? Unless you need the {{initiator}} information this may be a simpler approach.

Kind regards,
Bill

John Funk

Hi Jonathan,

You need to make sure that the atlassian-addons-project-access user has access to pretty much everything. Otherwise all of your add-ons will fail.

Jonathan Domanus

Sorry for the late reply here....

Looks like there was an issue with the add-on like you mentioned. My resolution was to create a new permission scheme from the one that worked, and then individually disable features until it broke. However once I got the correct permissions in place, everything worked as expected. So this appears to have been user error.

John Funk

Great! Glad you figured it out.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-desk-cloud

jira-software

jira-software-cloud