The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When I create a Sub-Task in Jira Portfolio Plans, it is created as Defect, instead of a Sub-Task, and all relationship to the parent is lost.
How can I avoid this?
I have tried adding all required fields to the layouts available to me (as suggested in this answer: https://community.atlassian.com/t5/Advanced-Roadmaps-questions/Bug-Added-Subtask-in-a-Portfolio-Plan-is-committed-as-a-Task-in/qaq-p/1146803) but the error persists.
The solution was very similar to the other issue. It was necessary to make some fields that were required in the project optional instead. I was unable to add them to the layouts, but when our Jira Admin made them optional, the problem went away.
So, solution for this type of problem in general appears to be: make any not-visible required fields optional.
Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.