The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bug - Added Subtask in a Portfolio Plan is created as a Defect in Portfolio for Jira

Laurie Koudstaal
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 1, 2021

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.

 

image.png

1 comment

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

Laurie Koudstaal
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 5, 2021

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.

TAGS
AUG Leaders

Atlassian Community Events