Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,291
Community Members
 
Community Events
184
Community Groups

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.


Action details:

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)

2 answers

1 accepted

0 votes
Answer accepted

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!

Hi! Yes, you needs to add Project Role (atlassian-addons-project-access)
This solution helped me.

@Aleksandr Khandogin that reply makes no sense. Add WHO to the project role?

Z B
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 12, 2020

I have the same problem but not with cloud but server. Do you have any suggesstions?

@Z B 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

Z B
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 12, 2020

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.

@Z B What is the solution for this In the same branch can't automation edit multiple fields?

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

Suggest an answer

Log in or Sign up to answer