We are in the process of setting up service desk to be accessible via direct email and via an in house ticketing system.
Our trouble comes from the ticketing system. It generates a new email with the same subject when the issue is Created, Updated, and Closed.
Each update creates a new email but the subject stays the same and includes a ticket number.
Expected: I want to be able to group the Created, Updated, and Closed email types together.
Actual: New ticket is created for every email
There's no de-duplication in JIRA, it's not designed for that sort of activity.
You'll need to find or write something that can do this. I would reach for a new "mail handler" that will check for duplicate summaries (email subject), presumably within a particular time frame, and then make comments or drop the new incoming mail completely.
Is there a way to have it check for a duplicate section in the summary (email subject). Say for instance the email subjects could be:
Created -- This is my ticket -- #000001
Updated -- This is my ticket -- #000001
Notes -- This is my ticket -- #000001
But all three of these are pertaining to the same ticket. They are just labelled differently detailing the status of the update.
The duplicate section I am referring to of course is the "#000001".
Thanks
Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not sure if anyone from Jira reads this, but this is basic functionality, along with things like ageing incident reports and a number of other things. Service Desk has a long ways to go before it even resembles anything like professional customer support software.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Such feature would be greatly appreciated by me as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I created a similar feature request here: https://jira.atlassian.com/browse/JSDCLOUD-8463. Feel free to vote it up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.