How to store release information on a "FIX Version"

[Lars Polling]

We use the JIRA "FIX Version" representing the actual Release in production. How can we store critical information regarding the change in production on a "FIX Version"? For example:

- Change number (text field)

- Runbook (attachment)

- Impact (=list drop down field)

- Support checklist (checklist field)

- Etc.

If indeed no data can be stored on the Version, what can be seen as alternative solution or best practice?

[Ian D]

Like Todd, we have task type of "Release" which has screens and custom fields to meet our needs, Thus, it go through a workflow too, as basic or sophisticated as you need. Bung your release documentation, artifacts in that.

[Todd Aspeotis]

At our company, we like to store the dates a release went to our first group of customers, our second group of customers and then we have a public release (we stagger the release).

To do this we created a new issue type ("Release") and we have three per fix version, one for each group of customers. It's the responsibility of the system admin deploying the release to update and close the issue once the deployment is done.

[Jobin Kuruvilla [Adaptavist]]

JIRA doesn't support adding metadata on a release without coding. You will have to customize the code. Or may be create a new custom field type that can be used instead of fix version!