You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Within this project we are working on, the uses would like to have two fields.
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?
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.