During the manual merge, you can enable the sync of the next comments from source to target issue. The common use case is incidents and a problem relation. After first merging data from one incident to the problem, we usually want to have everything under the problem, even the comments that will be added later.

Steps

1. On the source issue, click on the More dropdown. Select Merge action

2. To enable sync comments, click on Sync next comments on the merge screen

3. Proceed with a merge by clicking on the Merge button

Result

All information connected to sync comments is visible on the Synchronization panel on the issue. To stop sync, click on the pause icon.

Steps

• On the source issue click on the More dropdown. Then select Merge.

• When the Merge Dialog opens, select Target issue(s) and choose what fields and custom fields will be merged (you might also click Use preset to simplify your actions). You can also choose option from inlines Merge also and/or Actions after merge.

• You can enable Sync next comment. Read more about this feature .

• To finish the merge, click on the Merge button.

Actions are the doers of your rule. They allow you to automate merging and make changes within your site, and can perform many tasks, such as editing issues, merging them, or adding comments.

• Add reporter of source issue as watcher in target issue

• Add reporter of source issue as request participant in target issue

• Link source and target issue with link type

• Transition source issue to status

• Transition target issue to status

• Add comment to source issue

• Add comment to target issue

• Merge selected fields

• Merge fields as comment

Every rule starts with a trigger. They kick off the execution of your rules.

The app supports Issue created. It means that the rule will run when an issue is created in the current project.

👋 Welcome to Issue Merger

With Issue Merger app, you can find and merge duplicated issues, reduce the number of issues with the same root cause, and clean up your Jira instance. Using dedicated automation, you can merge similar issues automatically, without any additional analysis from the users or service agents' side.

🏗 How does it work?

Fully integrated within Jira, every user can select issues to merge with another one. In the merge dialog, choose fields from the source issue which values you want to add to the fields in the target issue. The second merging option is defining automation rules by the project administrator, so every matching issue is merged by our app.

🔑 What are the key features of the Issue Merger?

Features include:

• Manual merge option in a simple dialog on the issue or on the workflow transition

• Support for system and custom fields, also from Jira Service Management

• A definition on which status merging can be done

💪 What are the key benefits of using the Issue Merger?

Key benefits of using Issue Merger include:

• Keep your Jira tidy - Clean up your projects by merging duplicated tickets. Do not store similar issues that artificially increase their number in the backlog.

• Stay up to date with customer comments - Merge duplicated requests without losing the context. Select a synchronization option on the merge dialog. All new comments from source issues will be automatically synchronized into target issues.

• Reduce the risk of mistake - Manually copying values between two or more issues may result in the loss of valuable information. Focus on selecting the correct fields to merge, and leave the copying of these values to us (and our app).

Steps

1. Click on Settings (cog icon) > Manage apps

2. Under Issue Merger click on Auto-merge

3. Click Add rule

4. The rule configuration opens:

   • Click on the New rule to put a name for your rule

   • Click on the text field under the New rule to put a rule description (optional)

   • Change the toggle status if you don't want to enable the rule immediately after creating it By default, the toggle is set to on.

5. Click Save to save the rule

🎉 Result

The new rule has been saved and added to the list.

Presets are templates, thanks to which you can save selected fields to be merged and use them multiple times.

How to add presets​

🐾Steps

1. Choose Settings (cog icon) > Apps

2. Select Issue Merger Pro > Presets

3. Click

Steps

1. Choose Settings (cog icon) > Manage Apps

Steps

1. Choose Settings (cog icon) > Projects > Select your project

You can specify conditions that must be met for your rule to continue running.

Conditions can be placed after triggers in the rule chain. If a condition fails, no actions following it will be performed. It's required to select at least one condition to save the rule.

You can choose between meeting one or all of the listed conditions. Just click on the word "one" to switch to "all" and vice versa.

Summary

• Summary contains text

• Summary contains summary of source issue

Description

• Description contains text

• Description contains Description of source issue

Priority

• Priority is equal to

Labels

• One label is the same as in the source issue

• Labels are the same as in the source issue

• Labels contain any from selected labels

• Labels contain all selected labels

Components

• One component is the same as in the source issue

• Components are the same as in the source issue

• Components contain any from selected components

• Components contain all selected components

Text field / text area

• Text field or text area is the same as in the source issue

• Text field or text area contains text

Single selects, multi selects, radio buttons, checkboxes

• Single select, radio buttons, multi select or checkbox field is the same as in the source issues

• Single select, radio buttons, multi select or checkbox field contains any from the source issue

• Single select or radio buttons field contains all selected options

• Single select or radio buttons field contains any from selected options

Number custom field

• Number field is the same as in the source issue

• Number field equals to chosen number

• Number field is greater than chosen number

• Number field is less than chosen number

Issue Type

• Issue Type is the same as in the source issue

• Issue Type is equal to

• Issue Type contains any of selected options

Customer Request Type

• Customer Request Type is same as in source issue

• Customer Request Type is equal to

• Customer Request Type contains any of selected options

Other

• The issue key must appear at least in one of the selected fields

• Issue selected as target has one of given statuses

• Created within given hours

Steps

1. Choose Settings (cog icon) > Manage Apps

2. Select Issue Merger > Manual Merge History

3. Last 100 merge operations are displayed on the page

Difference between Replace and Append

Replace removes the old value and save a value taken from the source issue. Append adds selection to existing value (if possible).

System fields