Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Project ticket type question

Our company is currently on version 8.5.1 and I was wondering if the following ticket structure is capable on that version.
I have need for a ticket type that offers 3 different types of processess. For instance, our customer support ticket, would have a type of "DMS" and when creating that ticket, you would be asked (drop down) if ticket is for Adding, Removing or Changing the DMS. Each of these sub types would have their own work flow and subtasks. Is that possible?

1 answer

Hi @cgoodin

welcome to the community.

Based on your description, I'm assuming you're talking about Jira in an on-premise installation. If you refer to customer support ticket - are you talking about Jira Service Desk (now called Jira Service Monitoring)?

For Jira Service Monitoring/Desk, this could be a suitable solution:

Inside a JSM project, you can create various request types. Every request type will appear to the user as a new option to select. You can also group these request types logically together.
So, you could group all your DMS actions together and create 3 request types, Add DMS, Remove DMS or Change DMS.

Here's a screenshot from the Atlassian docs how that might look like.


By associating every request type with another issue type, you can then go ahead and assign to every issue type another workflow according to your needs.

I hope this helps.


Actually, I was referring to a ticket type (or project) within our Jira that we document all of our customer support tickets. We have the ability to create a customer support ticket and then choose a drop down of what type of ticket it is. My question is, if i were to choose a type, could that type provide another drop down option for that particular ticket type that based off which option you chose in the additional drop down, 3 different workflows and list of subtasks? 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events