nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Associate inbound email with existing ticket, don't create new ticket

Gamal Lear

Hi there. We're in the process of migrating from Freshdesk to JSM Premium and will be migrating all our existing tickets across. As part of that migration process, we will put the Freshdesk ticket ID into a custom field on the issue within JSM, so we have a record. The challenge we have is that once we go live on JSM, if any customer sends an email on a ticket that was originally opened in Freshdesk, then the subject line will have the Freshdesk ticket ID in it, not the JSM issue key, meaning that JSM will consider it a new ticket, rather than a reply to an existing open ticket (that was migrated).

Is there any way of considering these emails as replies to the tickets that are open in JSM via the migration, through some sort of automation rule or similar? I had hoped we could look to match the presence of the FD ticket ID in the subject line with the same value in the custom field of the JSM issue and use that to identify the issue to associate the email with, but I'm not sure if that will work or if there's a better option: I imagine this must be a common challenge for businesses where it is not possible to duel run on 2 ticket systems (as some of our tickets remain open a long time).

Any help/suggestions gratefully received!

Accepted answers

Kris Dewachter

Hi @Gamal Lear ,

It happens that i'm currently working on a similar issue. I've solved this with a simple automation rule that is triggered once a new ticket is created in Jira.

The rule will try to retrieve the ticketnumber from the summary by using substring in a smartvalue. Ex. {{issue.summary.substringAfter("#")}} (in this example, the ticketnumber appears after the #-sign).

Then, i added a branch in my automation rule that finds the ticket by using a JQL

Once found, I add the content of the trigger issue as a comment to the existing ticket.

Then, I delete the trigger issue.

Hope this helps,

Best regards,

Kris

All comments

Kris Dewachter

Hi @Gamal Lear ,

It happens that i'm currently working on a similar issue. I've solved this with a simple automation rule that is triggered once a new ticket is created in Jira.

Then, i added a branch in my automation rule that finds the ticket by using a JQL

Once found, I add the content of the trigger issue as a comment to the existing ticket.

Then, I delete the trigger issue.

Hope this helps,

Best regards,

Kris

Gamal Lear

Hi Kris, thanks so much for taking the time to share that, it certainly sounds like what we are looking for! Would you be kind enough to share a screenshot or two of the JQL and the rule step for adding the contents of the trigger issue as a comment on the existing ticket? Given it's working well for you, I'd love to replicate the exact approach and do some testing at this end.

Thanks again,

Gamal

Kris Dewachter

Hi @Gamal Lear ,

Sure. After the trigger, I use a "Create Variable" action to extract the ticketnumber from the "Summary" of the ticket. In this example, the ticketnumber appears after the #-sign.

Screenshot 2024-03-28 at 16.36.25.png

I also save the "Description" in a variable.

Screenshot 2024-03-28 at 16.37.00.png

Then I create a Branch and use a JQL command to retrieve the ticket. The JQL will be different in your case because you store the ticketnumber in a custom field.

Screenshot 2024-03-28 at 16.40.25.png

Screenshot 2024-03-28 at 16.42.11.png

And I use the "Add Comment" action to add the description as a comment to the ticket

Screenshot 2024-03-28 at 16.43.16.png

Best regards,

Kris

Gamal Lear

Thanks again Kris, that's awesome. All makes complete sense. Just one final question if I may! In my situation, the email subject has the Freshdesk ticket ID that following the format [#123456] - so I want to extract the 123456. Substring can be used like you suggest but I end up with 123456] - do you know the syntax to drop the trailing ] after the final digit?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management