nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Release Approval

Santanu Basak

Jira has release option where user can release version. I need a approval process before version release.

Before release the version I will send email to customer when customer approve from his email administrator will receive an email then he will release that version.

Accepted answers

All comments

Angélica Luz

Hi Santanu,

Currently, Jira SW does not have the option to add approvals for release.
We have a feature request suggesting the implementation of such ability:

- https://jira.atlassian.com/browse/JSWCLOUD-16329

Please, make sure to watch and vote to receive updates about the feature.

Regards,
Angélica

Amaresh Ray_lrrs4g

Hey @Santanu Basak ,

I'm a product manager at Atlassian looking to better understand your use case for approvals on releases.

I would love to chat with you - please send me an email at amaresh.ray (at) atlassian.com and I'll set up some time to speak.

Amaresh

Priyanka Patil_v7xwox

Hello Amaresh,

Can you please help us also with same feature we are also looking for?

Thank you

Ivie

Hi,

Checking to see if approvals on releases has been implemented.

Thanks,

Ivie

Pedro Silva_9jlf3t

This is now a MUST HAVE feature for companies who want to get ISO27001 certification

Pedro Silva_9jlf3t

This is now a MUST HAVE for companies who want to get iso 270001 certification

Pedro Silva_9jlf3t

Unfortunately this feature is very incomplete. There are key features missing:

1. You can add approvers but it fails to notify him/her/them once added
2. They can mark as APPROVED but this triggers no notifications, at least to the PM and Proj. Admins or the list of contributers
3. Without proper notifications, it is useless
4. One other aspect is the lack of a proper configurable workflow (In most software companies, a release goes from a range of statuses, such as:

NEW (creation)
QC DONE & ARTIFACTS READY
SUBMITTED CHANGE APPROVAL
APPROVED FOR GO LIVE
DEPLOYMENT IN PROGRESS
DEPLOYED LIVE
CLOSED
DECLINED

5. One of the MOST CRITICAL features is recording and seeing the date/time of these actions. Especially when it comes to the approval date/time. Not to mention the history of any transitions or changes.

In short, if Jira wants to be on top of the game regarding the deployment process, as well as compliant with ISO 270001, these are MUST HAVE features.

David Berclaz (Apwide)

What I’ve seen at most companies is a Release Management project, with a Release issue type, having an approval workflow like the one you mention.

The challenge is that these Release issues cannot have fixVersions with versions from other Jira projects. For that, I’ve seen different options:

- The Release issue type link Epic/Release issues in the respective Jira projects, that are then linked to the version with the fixVersion field.

- The versions have a prefix and are duplicated in the Release Project AND specific Jira projects (that are usually by Application or Team).

So like you wrote, there is still a way to go for Jira to be ISO270001 compliant without customization 😉