All Collections
Business requirements, user stories and feedback
JIRA integration
Jira integration: Release to FixVersion synchronisation
Jira integration: Release to FixVersion synchronisation
How to use the Release/FixVersion syncing in the Jira integration; Jira; Releases; FixVersion; Syncing; Integration; Field Mapping;
Oliver Jeffcote avatar
Written by Oliver Jeffcote
Updated over a week ago

Article Overview


  • Jira Dev Project connection in your Elements space

  • Issue type added to the Dev Project

Setting up Release to FixVersion field mapping

To set up the Release to FixVersion field mapping, go to the issue type(s) you have connected to Elements stories/requirements.

Under the "JIRA fields mapping" header, in the right hand column, find the "Release" field settings. From here, select "Fix versions" as the Jira field and select either one way or 2 way mapping, according to which way you want the integration to work. That's it, you're done!

How it works

The way this works is pretty simple. From Elements to Jira, when you send a new work item to Jira it will create a new FixVersion matching the Release name (if it does not already exist). Equally, from Jira to Elements, when a story is assigned a new FixVersion, we create that Release in Elements using the same name. In Elements, the release will show all the other work items in Elements with the same Release/FixVersion assigned to it.

Additional notes

You will see that you can choose from other fields to map the Release field to. Please note that if you select any other field than the FixVersion field the integration will not create new FixVersions in Jira, but the field value will still populate as a string.

We strongly recommend mapping FixVersion to Release in order to take advantage of the full capability of this feature, but we have left it flexible to meet your needs.

You might also be interested in

Did this answer your question?