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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bug - Added Subtask in a Portfolio Plan is committed as a Task in Portfolio for Jira

I'm trying to add subtasks underneath a task in my Portfolio for Jira plan. Adding them to the plan is working as designed, but as soon as I want to committ them to Jira through the Review button they will get created as new Tasks.

See below screenshot for the result. As you can see in the review changes screen the subtask issuetype is listed, but while committing them to Jira the pop-up selects the Task issuetype without the ability to change it to a subtask, although it is part of the issuetype scheme.Capture.PNG

Any idea what could be the issue? The Portfolio Hierarchy is configured correctly.

1 answer

1 accepted

1 vote
Answer accepted

Hi Robin,


Thanks for getting in touch, I hope I'll be able to help with your query.


I haven't been able to replicate this issue type mismatch on my own instance, but I have a hunch that this may somehow be related your required field configuration.


Looking at your screenshot, I don't think you shouldn't be seeing this 'Set required fields' dialog at all, as the issue type, project and summary fields have already been set - this issue should commit to JIRA without any further input required. The only reason I can think that you may be seeing this is if your field configuration contains a required field that is not associated with your project screen. What happens in this scenario if you click 'create'? Do you get an additional error about a specific required field not being set?


It would be helpful to get an idea of any other required fields you might have in your field configuration.


I look forward to your response,



Jira Portfolio team

Hi @Emma Ysebaert

Thanks for your help!

The issue was indeed caused by a required field (priority). After making it optional the issue was not caused anymore in Portfolio.

An interesting thing though when I faced the issue was that Portfolio gave no error but created a Task (instead of a Sub-Task) underneath the Task in the Portfolio Hierarchy. In Jira you couldn't see the same situation. So I would have expected Portfolio to give me somekind of error. Maybe something to look into?


@Robin Klein glad we got to the root of the cause!


I'm very interested in working out why this was displaying a task issue type instead of sub-task. I will investigate further and try to find a way to have a meaningful error displayed.




Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

To see this feature in action check out our recent dependencies demo here: Keeping on top of your dependencies is a key part of ensuring project success....

119 views 2 6
Read article

Community Events

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

Events near you