I imagine the rule is something like this..
Here are example Summaries:
First Issue:
Followup Issue:
*Because the follow-up request came in, I want to close both.
Any wizards out there?
I was able to solve this by using some fancy smart values and custom fields.
{{issue.summary.substringBeforeLast("o")}} -> Hello W
Hi Travis,
I'm having the same issue as you. We are currently forwarding all requests coming from an external HelpDesk system to our Jira Service Management. If the user replies to the issue, it will automatically create a new issue in our JSM and it usually contains the same HelpDesk Id ("RE-XXXXX").
Example:
First issue: TR :[Request ID :##RE-18215## - Accès A/P Aging detail grouped SAS]
Second issue: TR : Request ID :##RE-18215## - Accès A/P Aging detail grouped SAS - has been Re-Opened by the user.
I have been trying for hours to fix this. Do you mind telling me exactly what you did to solve your issue? Or help me resolve mine?
Thanks much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You may also want to look at OpsGenie for this. We generally don't have emails go straight to jira. We send to opsgenie which can can do a good job filtering and auto-closing alerts. then using OEC or the JSM integration, have opsgenie open the ticket in your jira.
Might save you from opening a lot of useless tickets.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andrew,
That was our first approach-- but we decided to NOT go with JSM Premium and thus, don't have the ability to add external integrations in OpsGenie. Thanks for your input!
Travis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.