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; } } }

INCOMING CUSTOMER EMAIL REQUESTS

unknown

Hi, would you be able to advise me of the best way to set up my Jira Service Project so that incoming customer emails automatically go into either - Incident, Problem, Service Request or Change queues please?

Currently they sit in the All open tickets queue - I can move them manually through to other queues but wondered if there was a clever way to do this please.

Thank you

Accepted answers

All comments

Velizar Borisov

Hi Lee,

Email created requests have only Summary and Description fields filled, which represent the email's subject and body respectively. How do you determine which email is for incident, problem, service request or change request queue?

unknown

Hi, thank you for getting back to me so quickly. At present we read through the emails, make a decision and then manually move them. I was just wondering if I asked the customer to type incident, problem, service request or change request in the title of the email it would help Jira and place it in queue for me. Thank you for you help.

Brant Schroeder

@[deleted]

Welcome to the community.

I would suggest implementing the portal and moving away from email. If you push the portal with your customers you will be able to setup different request types, collect additional information needed to resolve the request and better route requests. There is really no way to automate or route an email based on an email that comes in unless you use specific key words in the summary, etc. The way to go is using the portal.

Velizar Borisov

It is possible to achieve that just by editing the filters of your queues. For example, in your queue where you have the criteria of [ "Customer Request Type" = Incident] , just extend it to : ["Customer Request Type"= Incident OR "Summary" ~ 'Incident ']. This will help you to catch emails with the word "incident" in the subject.

However this approach requires some additional training for your customers to include key words in their emails and may not be the best around.

I would recommend sticking to the portal like Brant said, because it is easier to route the requests and the amount of mistaken user requests will be definitely decreased.

unknown

Hi Velizar, Great! Thank you for your help!

unknown

Hi Brant, Thank you. Yes, we are trying to look into this and understand it now. Would you be free to jump on a call sometime please? Thank you for help.

Brant Schroeder

@[deleted]

This is community support and community members to not work for Atlassian, we are just here to help others. If you would like to have a call with someone then you will need to submit a support ticket here: https://support.atlassian.com/contact/

If you have other questions please feel free to post them and we can help answer them.

unknown

Hi Brant, No worries, thank you for getting back to me, I appreciate your help!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

queue

jira-service-management