I would like to create a rule in Automation which is based on the fact that when a user creates an incident of a certain type, it can only be seen by the reporter and a group of users that is already defined in a group. This is possible? I've looked in the documentation and can't find anything that comes close.
Thanks!
Hi Nicolas,
You cannot create a Security Level on the fly - it would already have to exist. But if it does, then, yes, you can use Automation to update the issue to assign an existing Security Level to it.
I have already created the security level, but in the options that Automation gives me, I would not be finding the right one. Maybe it exists but I can't find it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you give some more details?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Right now we solved it this way:
From project settings/Issues/Security and from there good security level created.
Then I noticed that you can do it from Automation but from the Action and edition of the Security field. I just tried it, it came out perfect!
Thank you very much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great! Glad that worked for you!
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.
Yes, this is possible. You would be looking to use if/else JQL statements and action edit issue fields (i.e security level).
Don't forget to ensure 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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.