Can users create Automation rules in Automation Studio without Project Admin permissions? Additionally, can they associate the same Automation rule with multiple projects without having Project Admin permissions?
@Vikrant Yadav what would be the use case here? 👀
I mean - Studio should (and does) respect permissions and the same logic as automation within each space. Meaning, regular users cannot create automations within a space if they're not space admins. With what you're asking, they could be 'regular users' in the space and in Studio, and then 'override permissions' within one or multiple spaces.
Like, I think space admins wouldn't want that 😅
This is the general logic that applies to Automation platform as well as it should in Studio:
|
Action |
Required Permission |
|---|---|
|
Create rule for one space |
Space Administrator |
|
Create rule for multiple spaces |
Jira Administrator |
|
Manage Global Automation Studio |
Jira Administrator |
Cheers,
Tobi
Thanks @Tomislav Tobijas For your response!
I am looking for Rovo Studio Automation, as per the documents it seems that any user which have "Automation creator: This role gives a user permission to create new automation flows." Can create flow in any project. it won't respect the project admin permission.
User can create automation for any project and run or update field values.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Interesting @Vikrant Yadav 👀
They should definitely state that more clearly; especially in the docs for automation, so that Studio can override it.
I'd rather it respect permissions and the requirement for space admin, but I guess we'll see where this will end up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Vikrant Yadav
It depends on which tool you're using. In Rovo Studio, users don't need Project Admin rights, just the "Automation creator" role (though actions still respect their Jira permissions). Traditional Jira Automation is stricter, requiring Project Admin rights for single-project rules and full Jira Admin rights for multi-project ones.
Manage who can create in Studio | Rovo Studio | Atlassian Support
Use Rovo Studio in your organization | Atlassian Support
Cheers,
Arek🤠
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In Rovo studio, user can create Automation rule for any project ?
and map multiple project with a rule ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The user still needs to have access to the space (project).
Rovo including Studio respect permission on the user in the Atlassian realm, so the actor of the rule needs access to where the rule is running.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If a user only has Create Issues, Browse Projects, and Edit Issues permissions, they are still able to create automation rules for that project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then its Dumb solved because it should Respect Permissions. That's for me pretty much like Inconsistency.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
you can find that information here: https://support.atlassian.com/cloud-automation/docs/permissions-required-for-jira-cloud-automation-rules/
Regards
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.