The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Set Security level with Automation rule

Mackowiak
Contributor
June 30, 2020

Hello, 

I would like to base security on a custom field value = Site (S1,S2,S3)

User are part group S1, S2, S3 and should not see issues belonging to other Site

I'm trying to implement Automation rule at Creation step telling 

If Level is empty and Site = S1 then Level = S1

elsif  Level is empty and Site = S2 then Level = S2

 

it fails while running by "No fields or field value to update for the issue (may be due to field value missing for a given project ) :

Regards, 

Guillaume Mackowiak.

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
John Funk
Community Champion
June 30, 2020

Hi @Mackowiak ,

Make sure that the atlassian-addons group has permission to set the security level in the Permission Scheme. 

John Funk
Community Champion
July 1, 2020

Great! Glad it worked for you!

0 votes
Mackowiak
Contributor
July 1, 2020

Hi John,

You were right, I gave permission Security autorisation  to addon-group then I gave Issue security access to addon-group.

It works perfectly.

Regards, 

Guillaume.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events