Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JSM - How to create different queues based on email that the user sent it to

Dan Langenberg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 31, 2025

I have just recently started using JSM as a Customer Support tool for our SaaS business. 

I have 2 different email addresses added to the email channel. 

Example:
support@example.com
vipsupport@example.com

Right now when a customer emails in a support request there is no way for me to tell which email address they sent it to. 

The goal is to have different queues that the support agents can use to view the requests and that they know the VIP requests are priority. 

how do I set this up?

2 answers

1 accepted

4 votes
Answer accepted
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 31, 2025

Hi @Dan Langenberg 

Welcome to the community.

Have you considered dedicating a Request Type to each email? You can use this field for filtering, dashboards, and more.

How This Would Work:
Each incoming email address would be linked to a specific Request Type in JSM.
You can then filter tickets using JQL, dashboards, or reports based on the Request Type. 

Steps to Implement:
Create Separate Request Types

Go to Project settings > Request types
Add a new request type for each email (e.g., "Support Request - Email1", "Support Request - Email2").

Configure Email-to-Request Type Mapping

Set up different incoming email addresses in Project settings > Email requests.
Assign each email to a specific request type.

Use JQL to Differentiate Tickets

Once this is set up, you can filter tickets like:
"Request Type" = "Support Request - Email1"
This allows you to easily see which tickets came from which email.

 

Pros & Cons of This Approach

Pros:

Simple to implement.
No need for custom fields or automation rules.
Works natively with JQL and dashboards.

Cons:

Requires setting up multiple request types (can get messy if there are many emails).
If request types are used for other purposes, this could complicate workflows.

Would this approach work for your?

Dan Langenberg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 31, 2025

Here is where I am stuck:

  1. I have setup additional Request TypesStep 1.png


  2. I connected emailsStep 2.png

  3. When I go to remap the request type it only shows 2 options even though I have created more request types. Step 3.png

I tried undoing and redoing this and I am stuck

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 31, 2025

Hi @Dan Langenberg 

I can pick any one of the request on my side.

Do keep in mind the request types can only have the fields Summary and Description, no other fields or a form.

Dan Langenberg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 1, 2025

This ended up being the issue. Thanks for pointing that out. Now that I changed the fields I am able to select my new request types from the drop down. 

Thank you!

Like Laurie Sciutti likes this
0 votes
Dan Langenberg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 31, 2025

Thanks for this suggestion. I think we will try this. I will let you know how it goes. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events