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; } } }

How to add a custom field to versions

Thomas Augustinus

Hi,

I would like to add a "Release type" to all versions. Ex. Alpha, Beta, Production release (fixed single selection list).

My idea is to add a custom field that must be set on each version in any project.

Is that possible? Or is there another way to specify the type of a release ?

Thanks

Thomas

Accepted answers

Lenin Raj

Hi @Thomas Augustinus

Releases/Versions doesn't support custom fields, atleast not in the cloud version. One alternative is to suffix your version numbers with the type of release. Eg. `v1.5-alpha`.

Margaret Boisvert_ywjboq

We have overcome this issue by creating an issue type called Deployment Task. It requires the FixVersion field (only one value) and has several other custom fields that pertain to the release. By using the specific issue type, we are only storing the custom fields on the specific issues. This works well for us and allows automation to Release the version and close the tickets in the release when the Deployment Task is marked as done.

All comments

Lenin Raj

Hi @Thomas Augustinus

Releases/Versions doesn't support custom fields, atleast not in the cloud version. One alternative is to suffix your version numbers with the type of release. Eg. `v1.5-alpha`.

Fernando Bordallo

Hello @Thomas Augustinus

Your idea to add a custom field that is required to be filled in is correct. The fact that you call it Release or Version will not conflict with the existing versioning functionality available.

Just add the custom field to your issue scheme and ensure it is required and limited to a discrete set of options