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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
So I'm not talking about individual issues being converted but the actual Sub-task issue type now shows up as a standard issue type. I'm working with a new customer and novice admins so I'm not sure how it happened. It is a relatively new setup so no subtasks are currently created. Is is safe to delete and then recreate the Sub-task? Is there anything hardcoded to that Sub-task class/id?
You can't simply promote a subtask to be a standard issue type. Someone could rename the old subtask and have created a new standard task with the same name. And most likely moved all issues to the new task.
I would recommend for you to create a new subtask with you name of your liking, and move then back to being a subtask. However, the most difficult task will be to find out which the parent task was.
How many tickets are there?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.