Supported by the people who built it.

Jira has no way to add a public comment, add a participant or close a request without its own customer emails. The settings page and the preview say which ones to expect.

Requests are merged within one service project only, up to 10 duplicates at a time.

The app can't undo a merge. The notes on both requests and the log say what was copied, so it can be undone by hand.

Copies are made by the app, so Jira's history shows the app. Each copy names the agent who merged. Copied files show the merge date, not the original upload date.

Files over the limit (1 to 25 MB, 10 MB unless changed) are left out and listed, so the agent can add them by hand.

Satisfaction ratings, SLAs, time logged, history, approvals, web links and Confluence page links stay on the duplicate.

The app works through Jira's atlassian-addons-project-access role. If a permission scheme leaves that role out, or a workflow condition hides the done transition from it, the merge stops at that step and leaves the duplicate open.

The resolution is set only if the Resolution field is on the done transition's screen. If not, the duplicate is closed without it and the merge says so.