Hi!
I have automotion rule it's trigged by issue creation, "if" validates by issue type and it edit Summary field. It's works perfectly.
But when I apply custom issue security, when tasks see only people in group, that rule runing with error. And it's don't changes the Summary field.
What can I do in this case?
Thanks.
Error type in the bottom.
The following issues passed:NC-792
No fields or field values to edit for issues (could be due to some field values not existing in a given project): NC-792
Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Summary (summary)
Ok! If somones have same problems, so you may add to issue security Project Role (atlassian-addons-project-access).
Hi @Aleksandr Khandogin - I have the same issue now, where do I add what you are suggesting - the ''may add to issue security Project Role (atlassian-addons-project-access). ''?
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi! Yes, you needs to add Project Role (atlassian-addons-project-access)
This solution helped me.
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.
I have the same problem but not with cloud but server. Do you have any suggesstions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Zita Bagi I don't know how it works at server version, but I guess in server version settings should be similar.
You should add to issue security access for addons in project role.
In Cloud version this access for addons named "atlassian-addons-project-access", in server version maybe different
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, it's probably not that because one branch of the automation works and the other doesn't. I have contacted Atlassian support because I couldn't figure it out.
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.
I get the same error (No fields or field values to edit for issues (could be due to some field values not existing in a given project) This happens for a Custom field but only on "some" tickets. On most other tickets, the automations runs and updates this custom field. The atlassian-addons-project-access has permission to edit issue. Issue Security is not enabled on this project. The automation has only if else and no branching. Any help is welcome. Thanks
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.