Benefits and Behavior

With version sync you have the possibility to store every version in a single issues and sync them with the release sections of your Jira projects. The benefits are:

• assign version issues to responsible person of version

• have your own workflow for the version issue

• manage additional information over screens and customfields

• use normal version custom fields like "FixVersion"

• store version issues of a Jira project in the same Jira project or in a collective version project

• use agile boards to manage versions of products

You can add a synchronization for the project you want to sync and select, if you want to store the version issue in the same or in a collective Jira project.

If enabling a version synchronizer for a project, all releases of that project will be created initially as Jira issues. Afterward it is only possible to create, edit or delete version in the version issues. The synchronization updates the standard release list automatically, so that you can use this list for choosing fix version or for navigation.

Open

Open

Enable Version Synchronizing

Starting Position for syncing versions

You have a Jira project with planned or unreleased versions like the following - this is your source:

Prepare the following configurations in the project, where you want to store your version issues - this is your target project (maybe the same as your source)

1. Add a new issue type for Versions.

2. Add screen(s) for the Version issue type with the fields: Version Archive Status, Version Status, Projects for Version Sync, Synced Versions  - these are preinstalled with the add-on.

3. Add workflow for Version issue type.

Add a version syncronization

Open JIRA ADMINISTRATION → Add ons → STAGIL Assets and CRM → Synchronization → Version Sync → Manage

Fill out the Common Configurations:

• user account for the synchronization - you need to choose a user who has the create permission in the target project

• issue type - the issue type for the newly created version issues

• description field - the custom field where the description of releases are stored in the issue

• start date field - the custom field where the start date of releases are stored in the issue

• Release date field - the custom field where the release date of releases are stored in the issue

and click Save.

Next, choose a JIRA Project as your Source Project. From this project the releases are created as version issues. Choose a target project in the field to project. This is the place where the version issues from source project are stored. Click Add & Synchronize to add the synchronizations.

You can add as many synchronizer as you want.

Delete a version synchronization

If you delete a synchronization 

• there will be no changes in the releases of the source project

• the associated version issues are not deleted

• you can create, edit or delete versions again through the release list

• changes in associated version issues have NO effect on the releases anymore

• and add a new synchronizer with the same source and target project again, then new version issues are created

Working with versions

Add a new version of project

1. Create a version issue in the project where you would like to store your versions.

2. Fill out the summary of the issue with the name of your version.

3. In the custom field Projects for Version Sync choose the name of your Jira project the version belongs to. You can only choose projects with an enabled version synchronization.

4. Fill out more information in your screen, if needed.

Synchronizers automatically create new release entries in the standard Jira release list.

Edit information of a version

It is not possible to edit information in the standard release list. Please use the link below Actions to go to the associated version issue and edit the information via the custom fields of the issue.

Release a version

For setting the status of a version you can use the custom field Version status in the version issue. Choose released or not released. This information is automatically transferred to the standard release list.

Archive a version

For setting the status of a version you can use the custom field Version Archive status in the version issue. Choose archived or not archived. This information is automatically transferred to the standard release list.

Delete a version

You can delete a version, if you deleted the version issue. The version is automatically deleted in the release list.