Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,552,469
Community Members
 
Community Events
184
Community Groups

Issue type: Sub-task mysteriously converted/promoted to a standard type.

Brent Webster
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 19, 2017

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?

1 answer

0 votes
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 23, 2023

Hi @Brent Webster 

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?

Suggest an answer

Log in or Sign up to answer