Hello
I need to set an automatic rule when an issue is created depending on the group who belongs the reported the security level is set with a value.
when I create the issue I got errors in the automation
No fields or field values to edit for issues (could be due to some field values not existing in a given project)
Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Security Level (security), Region(s) (customfield_10300)
But the values and fields exist for the project as if I edit manually I can put the corresponding value.
thanks for helping me
Laura
Hi @Laura Ramos Rodriguez you should ensure that the field is editable (seems to be the case if I understood correctly) and that the user that is being used on the automation rule has the right permissions to set security levels.
Hello
I have assigned the permission to set the security level to the administrator project role .
I have this role and I am executing the rule when creating the issue.
I am also as owner of the rule.
In the documentation, I have read : "In your site, the rule actor will be set as Automation app user"
The automation app user is the "owner of the rule" , the user that is executing the action which has the rule or there is another configuration to set an user as Automation app user?
regards
Laura
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Laura Ramos Rodriguez make sure that the Project Role (atlassian-addons-project-access) has permissions to set security levels as well. It's the one used by the automation app user
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Hernan
Thanks a lot, you solved my issue, I didn't check if for edit issues this project role had permissions .
Now the error disappeared , I didn't get yet the results expected from the rule set, but i don't have errors.
thanks a lot
Laura
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Glad to know is working now.
Please don't forget to mark this as solved if it's the case.
Best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, we have Jira Core 8.5.3 and JIRA Service Desk 4.5.3. there's no Project Role (atlassian-addons-project-access), how can we solve this? Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Zita Bagi that role isn't created by default in server version. You must check that whoever the user configured in the automation rule has the right permissions over the project. In this case it would be another role within the instance
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, thanks. At this is probably not what's causing the issue because I can set security level in once branch of the automation, but not in another, so it's probably not a permission thing. I've submitted a support question to Atlassian, I'm still awaiting their response.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.