Thank you, but I'm sorry, I got another question: what's the current issue type of the issue you wanted to change to Sub-task? Is it already in the AUT-Project?
Are you able to change the type to another sub-task-type (escalation, sub-bug or sub-test) ?
Once, we had a problem with a main issue type that we accidentally called "sub-task". The project template treated our sub-task-type as a main issue type and a sub issue type, so we had somehow a standard type as subtype of another standard type. This led to really big problems in the generated project.
Maybe you got something similar.
I tried to move subtasks, it worked. I played around with Tasks/Subtasks - Subtasks/Subtasks. I get what I am looking for.
This is what I am thinking: A configuration change has been made (may be a task has been renamed.
It may sound annoying to you but can you repeat the steps you are trying and what are you trying to achieve?
@Fadoua Boualem and I, we talked about your issue. We both think, that you better should ask Atlassian support. They have more options to help you than we have here in the Community.
This is a really strange behaviour and we currently have no idea, what to recommend next.
Please contact Atlassian Support here: https://support.atlassian.com/contact/#/
If the problem is solved, it would be nice, if you could give us a brief update.
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events