Hello,

Please refer to this use case to rationalize this improvement request.

1. User creates a release candidate from a build (at this point a Bamboo deployment release has been created, e.g. app-1.0.0-rc.1) and promotes it across most deployment environments
2. Once QA and UAT passes, the release candidate is deployed to a "Publish/Production" environment which will strip off the release candidate identifier and build number leaving only the project name and the semver-specific three-digit notation for the version (app-1.0.0)
3. From there, the release is retagged, promoted to stable/staging repositories, deployed to production, etc...

At the end of this procedure, I'm left with a deployment project with a release history full of release candidates but no releases regardless if I had some published to production. I've been meaning to fiddle around step 2 and make mischief with the bamboo deployment variable bamboo.deploy.release in an attempt to rename a release but I don't think that will work.

Is this something that can be achieved with a special task or at least a routine I can access within the deployment project to do this?

Kind Regards,
Daniel