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

Two Issue Type Fields or Multiple Issue Type Scheme


Within this project we are working on, the uses would like to have two fields.

  • Field one - the standard issue type field with the options of choosing task and epic 
  • Field two - also standard issue type field with the options of choosing story and spike

Is it possible to actually have two issue type system fields on one screen?Is there any way in which one could do that?

If not, what would be the alternative so that you still get the functionality if you choose a specific issue type?

I assume it's not possible to have multiple issue type schemes associated within one project?


1 answer

1 accepted

3 votes
Answer accepted

No, that cannot possibly work.

Issue type is NOT a field.  It's a structural component of an issue.

An issue can only be of one type, it's nonsense to say "that issue is a bug and a story",   It can only be one or the other.  The issue type determines all the configurations of the issue as well, so having two of them would be nonsense - which configuration would you use if someone put two different 

But you can configure issue types differently - that's what they are for.  You can give them different fields, workflows, and screens amongst other things, and you can do it by project too, so a bug in one project works differently to a bug in another.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events