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
This question is in reference to Atlassian Documentation: Duplicate Issue Types from Default Issue Type Scheme
I have been experimenting with my JIRA Core Cloud instance. I have created a new issue and a new issue scheme. Now Task and Subtask are missing from the Default Issue Type Scheme. There doesn't seem to be a way do add them back to the Default Issue Type Scheme.
What's happened and how can I fix it?
My recollection is vague because this was some time ago. I wound up needing support from Atlassian. They had to make corrections in the database. To be honest I don't know exactly what they changed. I believe the problem was caused by some defect in the software. I do not know if it has been fixed.
Just found this issue recently and you know what?
Atlassian - this really underscores how absolutely cobbled together and shoddy your platform is!
The entire layout and association of schemas, projects, templates, and add ons makes it incomprehensible and completely convoluted.
YOU HAVE A BUG NOW DO YOUR JOB AND FIX IT! You owe it to all of your customers who have invested their money and time in to using this platform.
FIX IT TODAY!!
I see this in the latest version. I noticed it last week when I saw only Epic in the Default Issue Type Schemes and new issues in existing projects could not be assigned to anything else other than Epic and new issue type I created. I had to delete all the issue types in a project and then readd them from the list. However, these types (story, bug, task, etc.) are not on the Default Issue Type Schemes Screen.