Match source and destination objects

Introduction

Very often, our users don’t just want to deploy their snapshots as they are. They need to be able to match some of their configuration objects with specific ones on the destination instance in order to ensure all processes and workflows will work as intended after a deployment.

Well, we are giving you that power. For any supported configuration object, you can now choose the destination object that will match it accordingly.

Open

Supported objects

List of configuration objects supported by Selective Merge:

• Priorities and priority schemes

• Field screens, field screen schemes, and field configuration schemes 

• Custom fields and field configurations

• Notification schemes

• Issue security schemes

• Workflow and workflow schemes

• Permission schemes

• Statuses and resolutions

• Events

• Project categories

• Agile boards

• Filters

• Dashboards

• Users and groups

• Issue types, issue type schemes, issue type screen schemes, and issue link types

How it works

On the deployment wizard's Analyze phase, in the Analyze Configuration Changes list, you will see the option → M next to the supported configuration object. Clicking on this marker opens a dialog for you called Match to target object that allows you to choose how to deploy the snapshot element of interest.

To change how a configuration object is deployed:

1. Start a configuration snapshot deployment.

2. In the Analyze phase, navigate to an object’s tab (for example the Screens or Schemes tab).

3. Choose an object within it that has the option → M.

   Open

   

4. Click the → M option and then choose a target configuration object in the dialog.

5. Click the Analyze button to confirm the changes.

Configuration Manager will reanalyze the configuration to reflect the new modifications and will update the Analyze Configuration Changes page with the new information about the planned changes.

Merging many-to-one objects

When using the selective merge feature, you can have multiple source objects pointing to one destination object. We refer to this as the “many-to-one” merging.

This feature is only available for users and groups! It’s useful when you have multiple inactive users that you don’t want to bring into your other Jira instance but also don’t want to break any configuration objects by not including them in the deployment.

When you do a many-to-one merging, the destination user or group will be assigned to all the places where the merged users/groups were assigned (i.e. in issues, permission schemes, JQLs, etc.).

As with the regular selective merge, you need to click the Analyze button to confirm your changes.

Audit Log

Configuration Manager captures and provides information in the Audit Log about all the modifications made during the deployment. You will be able to compare the configuration elements before and after the changes.