Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In the example below we will create a project link with a project that has existing versions that we would like to keep:

Project: VCS - Source (team managed)

Versions: 1.0.0 & 2.0.0

Image RemovedVCS DC - Keep versions (1).pngImage Added

Project: VCS - Target 1 (team managed)

Versions: 1.0.0 & 3.0.0

Image RemovedVCS DC - Keep versions (2).pngImage Added

To share versions/components from the VCS - Source project, we will create a project link with project VCS - Target 1

  • Navigate to the Version & Component Sync page in the Source project.

  • Click on Create a project link

Image RemovedVCS DC - Keep versions (3).pngImage Added

Image RemovedVCS DC - Keep versions (4).pngImage Added

  • Select the project(s) you want to link to the Source project. Versions from VCS - Source will be propagated to selected project(s)

  • After selecting the desired projects to link to VCS - Source, click on Next: synchronisation

Image RemovedVCS DC - Keep versions (5).pngImage Added

Image RemovedVCS DC - Keep versions (7).pngImage Added

  • In this example we will use the default Scheduling

  • To ensure existing versions maintain in VCS - Target 1 we will uncheck the Delete trigger. All other triggers will remain checked.

    • Keep in mind that unchecking the Delete trigger means that none of the ‘Delete’ events will be synchronised. The deletion of a version/component in the VCS - Source project will no longer result in the deletion of the version/component in VCS - Target 1.

    • Unfortunately, there is currently no option which will preserve manually created versions/components in Targetproject(s) whilst also synchronising the delete events in Source projects to the corresponding versions/components in the Targetproject(s).


      This limitation comes from the fact that the app has no means to determine if a version/component was manually created in the Source project(s).

VCS DC - Keep versions (8).pngImage Added
  • Click on Next: filters

Image Removed
  • The app will now show an overview of the versions that will be synchronised from the source project to the target project

    • By creating filters you can control which versions are in-or excluded from synchronisation

    • In this example we will not use any filters

VCS DC - Keep versions (9).pngImage Added
  • Click on Next: confirmation

Image Removed
  • The app will now show an overview of the project link(s) you are creating

  • Click on save, to save the project link(s)

  • Upon clicking on save, the app will:

    • Start synchronising

    • Shown an overview of the created project links and their current status

Image Removed
VCS DC - Keep versions (10).pngImage Added
    Image Removed

    • To edit or delete a existing project link first navigate to the Version & Component Sync page in the target project or click on the Linked project link on the Version & Component Sync page in the source project

    • Click on the Settings tab

    Image Removed
    Image Removed

    • To provide you with insights in how the app works, this is what happens during synchronisation:

      • Upon creating a project link between Source & Target Project 1 the app checks whether there are versions present in Target Project 1

    Version 1.0.0

    • The app recognises that version 1.0.0 in VCS - Source already exists in VCS - Target 1

    • The app links version 1.0.0 in VCS - Source to version 1.0.0 in VCS - Target 1

    • This links ensures that any and all version changes to version 1.0.0 in VCS - Source are synchronised to version 1.0.0 in VCS - Target 1

    Version 2.0.0

    • The app recognises that version 2.0.0 does not exist in VCS - Target 1

    • The app creates version 2.0.0 in VCS - Target 1

      • Jira does not allow you to link a single version to multiple projects. Therefore the app needs to create ‘new’ versions in VCS - Target 1

    • The app makes sure that upon creation of the ‘new’ version 2.0.0 in VCS - Target 1 it is linked to version 2.0.0. in VCS - Source

    • This links ensures that any and all version changes to version 2.0.0 in VCS - Source are synchronised to version 2.0.0 in VCS - Target 1

    Version 3.0.0

    • The app recognises that version 3.0.0 in VCS - Target 1 does not exist in VCS - Source

    • Due to unchecking the delete trigger the app will not delete version 3.0.0 in VCS - Target 1

    Project: VCS - Source (team managed)

    Versions: 1.0.0 & 2.0.0

    Project: VCS - Target 1 (team managed)

    Versions: 1.0.0, 2.0.0 & 3.0.0