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

Too many issue type?

My user requests two additional issue types to be created in jira project which is "Question" and "Enhancement". Currently, we already have issue type "Improvement", so I have advised my user to use that instead. Should I create the "Question" issue type? Any impact if we create too many issues type and what is the best practices? Thank you for your advice.


1 answer

0 votes
Fabio Racobaldo _Herzum_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 23, 2023

Hi @Megan Liou ,

it depends form your internal organization. Btw, as you said, the best approach is to create new entities (issue type, custom fields and so on) just if strictly necessary.

Enhancement and Improvement should manage the same request so, in my opinion, you can use "Improvement". "Question" seems to be a different item with specific custom fields so it could be eligible to be a specific issue type.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events