The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Use of issue type

Florian Nock
July 31, 2018

Good evening,

if I understand correctly an issue type is connected to the type of activity of a request (it is a simple or complicated task, urgent or not, etc...). Could I, instead, connect the issue type to the subject of the request?

Often my customers do not have a clear idea of what their problem is, so I thought of creating few generic request types and then assigning an issue type which defines the problem in a more specific way. This would mean having more issue types than request types, but it would allow the agents to accurately define the problem and keep track of what the customer has chosen.

Do you think something like this is possible and useful?

Thanks a lot.

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Raynard Rhodes
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 Champions.
July 31, 2018

Issue Types can have Request Types

Issue Types also dictate the workflow

You can have a generic Issue Type and connect all the request types to it.

 

For reference: https://confluence.atlassian.com/servicedeskcloud/configuring-request-types-and-workflows-732528910.html

TAGS
AUG Leaders

Atlassian Community Events