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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.