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

VCS DC - Keep versions (1).png

Project: VCS - Target 1 (team managed)

Versions: 1.0.0 & 3.0.0

VCS DC - Keep versions (2).png

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

VCS DC - Keep versions (3).png

VCS DC - Keep versions (4).png

  • Select the project(s) you want to link to the Source project. Versions from VCS - Source will be propagated to selected project(s)
    In this example we will create a project link with VCS - Target 1

  • Click on Next: synchronisation
    In this example we will use the default Scheduling

VCS DC - Keep versions (5).pngImage Removed
VCS DC - Keep versions (7).pngImage Removed

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

Note
  • Keep in mind

that unchecking the
  • that unchecking the Delete trigger means that none of the

‘Delete’
  • Delete events will be synchronised.

The deletion of
  • This means that:

    1. Existing versions will not be removed from the Target project(s)

    2. The deletion of a version/component in the

VCS -
    1. Source

project will
    1. project will no longer result in

the deletion of the version/component in VCS - Target 1.
    1. the deletion of the corresponding versions/components in the Source project(s). 

      Unfortunately, there is currently no option which will preserve manually created versions/components in Target project(s) whilst also synchronising the delete events in the Source

projects
    1. project to the corresponding versions/components in the Target project(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
    1. Target project(s).

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

VCS DC - Keep versions (5).pngImage Added

VCS DC - Keep versions (8).pngImage Added
  • 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 synchronisatiosynchronisation. In this example we will not use any filters

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

VCS DC - Keep versions (10).pngImage RemovedVCS DC - Keep versions (9).pngImage Added
  • The app will now show an overview of the project link(s) you are creating

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

VCS DC - Keep versions (10).pngImage Added
  • Upon clicking on save, the app will:

    • Start synchronising

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

VCS DC - Keep versions (11).png

  • 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

  • VCS DC - Keep versions (12).pngImage Removed

    VCS DC - Keep versions (13).pngImage Removed

    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

    VCS DC - Keep versions (14).png

    Project: VCS - Target 1 (team managed)

    Versions: 1.0.0, 2.0.0 & 3.0.0

    VCS DC - Keep versions (15).png

    To edit or delete a existing project link:

    • 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

    • Navigate to the Settings tab

    • Here you change the apps synchronisation method, log lever or delete the project link all together

    VCS DC - Keep versions (12).pngImage Added

    VCS DC - Keep versions (13).pngImage Added