For Jira Service Management Cloud

Your queue stops filling with duplicates.

Customers write twice, reply to old threads, or three people report the same outage. Queue Tidy catches those duplicates the moment they arrive and merges them without losing a comment, a file or a customer.

Coming soon to the Atlassian Marketplace. Free for teams of up to 10 users.

Queue · Waiting for supportToday
SD-412VPN not connecting from homeOpen
SD-418Re: VPN not connecting from homeDuplicate · 97%
SD-405Fwd: VPN still downMerged into SD-412
SD-416New laptop for PriyaOpen

SD-418 arrived 6 seconds ago from the same customer. Queue Tidy flagged it as a duplicate of SD-412.

How it works

Jira Service Management has no built-in merge, and the request for one has more than 1,200 votes. Queue Tidy adds it, then goes further.

  1. Catch

    Every new request is compared with open tickets from the same customer. A likely duplicate is flagged within seconds, or merged automatically when the match is near certain.

  2. Merge

    The original request, every comment, attachments, the customer and participants move to the ticket that stays open. The duplicate is linked and closed.

  3. Keep customers informed

    The customer is told where to follow and keeps getting updates. If they reply to the closed ticket, the message lands on the open one.

Everything a merge should do

Duplicates caught on arrival

Flag for review or merge automatically, with a confidence level you choose. Email requests only, or every channel.

Merge into…, from any ticket

See the best matches, preview exactly what will move, and merge in the background.

Bulk merge and backlog scan

Review every suggestion on one page, merge many at once, and clean up duplicates already in your queues.

Late replies rescued

Replies to a closed duplicate are copied to the open ticket, even after a chain of merges, and the duplicate stays closed.

Nothing lost

Comments arrive as agent-only notes with the original author and date. Files up to 200 MB are copied across.

Time saved, measured

See duplicates caught, merges done and an estimate of agent time saved for each project.

Your data never leaves Atlassian

Queue Tidy runs entirely on Atlassian's Forge platform, with no servers or outside services of our own.

  • Built to qualify for Atlassian's Runs on Atlassian program.
  • Every action checks the agent's own Jira permissions first.
  • Only project admins can change settings.
  • No tracking, no advertising, no AI training on your tickets.
  • Read the privacy policy.

Pricing

Billed through the Atlassian Marketplace, by the number of users on your site. Planned prices, which may change before launch:

UsersPrice per year (US$)
Up to 10Free
25about 180
50about 360
100about 700
500about 2,400

Questions

Does it work with Jira Software projects?

No. Queue Tidy is built for Jira Service Management projects, where customers raise requests.

Will customers see the copied comments?

No. They're added to the open ticket as agent-only notes, with the original author and date.

Can it merge automatically?

Yes, if you turn it on. Start by flagging duplicates for review; switch to automatic merging for near-certain matches once you trust them.

Can I undo a merge?

Not yet. Undo is on the roadmap.

How do I get help?

Email support@queuetidy.com or see the support page.