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:
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great! Glad you figured it out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.