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: 

Issue type vs request type

Aldo
October 25, 2022

hello!

I'm trying to figure out best practices for issue types vs request types. Whether matching one to one, or use one issue type for multiple requests. Thanks in advance!

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

3 votes
Answer accepted
Brant Schroeder
Community Champion
October 25, 2022

@Aldo Welcome to the Atlassian community

This really depends on how your processes work and what the workflow is after the request is received.  

We usually try to minimize issue types since it makes changing the request type a little more involved as you have to move the issue instead of just changing the request type.  It also makes the maintenance of custom fields a little easier.  At the end of the day if we have a request that requires a unique workflow then we end up creating a separate issue type for it.  

Aldo
October 25, 2022

Thanks, Brant! This is helpful and my thoughts exactly since I have some automation created around it to make the switching of request types much easier. I will keep this in mind. Thanks again and for the welcome :)

Like Brant Schroeder likes this
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events