Hello!
We have a service account that automates part of our release process. As a release ships, it tags the relevant issues with a fix version (fixVersions), and we'd now like it to also create the version in the project if it doesn't already exist.
The issue tagging works fine with minimal permissions (Browse Projects + Edit Issues). But creating a version via POST /rest/api/3/version requires Administer Projects (or global Administer Jira), per the API docs, and that's far more than we want this account to hold.
Project admin lets it reconfigure the entire project; we only need it to create/manage versions.
Question: Is there any way to grant a user or service account the ability to create project versions without giving it full Administer Projects? For example:
- A more granular project permission we've missed?
- A project-role-based approach that scopes version management specifically?
- An OAuth/app-level mechanism (we authenticate via OAuth 2.0 with the write:project-version:jira scope, which is granted, the blocker is the project permission, not the scope)?
If the only option is Administer Projects, we'd rather keep version creation with an account that legitimately holds it and leave this automation account at least-privilege. But we wanted to confirm we're not missing a narrower path before designing around it.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.