Is there any update on this feature to have granular permissions for Releases minus granting Project Admin rights?

Would love this! Specifically creating releases

Motivado pelo comentário do usuário 8b875317998e onde ele comentou que criou uma solução 'paleativa' com automação, eu criei uma automação mais simples, que acredito que ajuda nessa situação.

Motivated by the comment from user 8b875317998e  where he commented that he created a 'palleative' solution with automation, I have created a simple automation that I believe helps in this situation.

Minha solução:

My solution:

ETAPA 1 | STAGE 1

• Criei uma automação com um "Acionador manual" que vai ficar disponível em todas as tarefas do projeto (a não ser que você queira restringir com algum critério, exemplo: para algum grupo específico)
• Nesse gatilho, eu marquei a opção "Solicitar entrada quando essa regra for acionada"
• Nas opções abaixo, eu adicionei um campo do tipo "Texto curto" e o nomeei de "Nova versão"
• Marquei a opção para ele ser obrigatório, e nomeei a variável dele para "NovaVersao"
  Obs: Na próxima etapa você precisará usar a chave gerada para o seu campo variável 

• I created an automation with a "Manual trigger" that will be available in all project tasks (unless you want to restrict it with some criteria, for example: for a specific group)
• In this trigger, I checked the option "Request input when this rule is triggered"
• In the options below, I added a field of the "Short text" type and named it "New version"
• I checked the option for it to be mandatory, and named its variable "NewVersion"
  Note: In the next step, you will need to use the key generated for your variable field 

ETAPA 2 |  STAGE 2

• Agora adicione ação "Criar versão"
• Em "Nome da versão", você vai usar a 'chave' gerada para o seu campo variável
• Não é necessário definir "Data de início", "Data de lançamento" ou "Descrição da versão"
• Em "Projeto", você pode definir o "Projeto" que gostaria que essa automação funcione, ou pode fazer com que essa automação seja global para todos os projetos (para isso, você precisa mudar o escopo na sessão "Informações da regra" da automação).

• Now add the "Create version" action
• In "Version name", you will use the generated 'key' for your variable field
• You do not need to set "Start date", "Release date" or "Version description"
• In "Project" you can define the "Project" you would like this automation to work on, or you can make this automation global for all projects (for this you need to change the scope in the "Rule Information" section of the automation).

FINAL

Em todas as tarefas desse projeto, será apresentado o gatilho (A não ser que você defina algum critério para a apresentação da automação), onde o usuário pode clicar, para adicionar uma nova versão. Neste meu exemplo, eu nomeei a automação de "ADD VERSÃO"

In all tasks of this project, a trigger will be presented (unless you define criteria for presenting the automation), which the user can click to add a new version. In my example, I named the automation "ADD VERSÃO"

Quando ele clicar, será apresentada uma tela, para ele informar o nome da versão que ele quer criar.

When he clicks, a screen will be displayed for him to enter the name of the version he wants to create.

Quando ele clicar em "Continue" versão será adiciona nas versões do projeto.

When he clicks on "Continue" version will be added to the project versions.

Observações gerais:

• Neste exemplo não existem validações se a versão já existe ou algo similar

Final considerations:

• In this example there are no validations if the version already exists or something similar

Hi 06cd3e1e75dc- Unfortunately at this stage the change will not be applied to Jira Data Center in the near future - please do continue to follow and support the relevant tickets to receive updates.
Cheers, Aditi

dcbd111bd252 What about the same for Jira data center?

Hello everyone,

I'm pleased to share we are now exploring this feature, and would love to invite you to take part in an upcoming customer research study!

What’s involved in the research:

Sessions are 50-minutes and conducted over video-conference, so you can participate from anywhere around the globe.

During the research, we'll start with a general chat to get to know you and dive into your use-cases for granular permissions.

As a token of our appreciation, you'll receive an e-gift card worth $100 USD within 5 business days of completing your session.

Interested in taking part? Follow this link to fill in a few more details so we can make sure you’re a good fit.

If you have any other questions at all, feel free to reply to this message or email me directly on adalal@atlassian.com. We look forward to meeting you!

Cheers,

Aditi Dalal
Jira Permissions Team

jthomas@atlassian.com the Extended Project Administrator is released https://www.atlassian.com/wac/roadmap/cloud/Extended-project-administrator-capabilities?search=extended%20pro&p=22eb26f7-ef How about this demand? It was created back in 2019! Come on, permission handling is really not that huge but it has a huge impact, the workaround is to provide admin permission to any team member.

jthomas@atlassian.com Version management (creating, releasing, archiving) is a day-to-day task just about any dev or PM can plausibly have a reason to do, especially in the "agile" world where releases happen weekly or even more often. The current state would be like if Linux or MacOS required root permissions to create a directory, or indeed if Jira required all users to be Jira Admins just to transition tickets.

1920 votes and 4 1/2 years at this time.

You last update on this highly desired feature back in February said:

"The team is currently working on Extended Project Administrator, and after this is shipped, we will consider Version Permissions."

As you can see by the link https://www.atlassian.com/wac/roadmap/cloud/Extended-project-administrator-capabilities?p=22eb26f7-ef this has now been released, so can we please have an update on if and when the feature we actually want, and need will be developed.

I think this feature should have been developed before the Extended Project Administrator feature as I would trust Project Amins to create their own versions, but I wouldn't trust them to adjust workflows that's why we have them in Company managed projects.

+1