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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Creating a subtask using the new issue view does not save the subtask issue type correctly

In Jira's new issue view, if you are on an Issue page and the issue has subtasks, you can click + to add a new subtask.  When you do, there is a dropdown to select the subtask issue type and a text field for the new subtask description.

When you click Create it takes you to the Create Subtask screen.  The problem is that the Issue Type field does not retain the issue type you selected from the main issue screen. Instead, it is defaulted to the last subtask issue type the user created.

This is leading to people frequently creating subtasks with the wrong issue type.

Is this going to be fixed, or has this already been reported?


1 answer

1 accepted

3 votes
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 12, 2019

Hello Christi,

Sorry to hear you are facing this problem.

Per your description, I can clearly understand that the sub-task issue type selected in the parent view is not carried over to the pop-up opened when finishing the sub-task creation.

Indeed, this is a bug with JIRA application that we've already reported to our developers:

Creating Sub-Tasks where create Sub-task screen is required does not preserve selected sub-task type 

Feel free to vote and watch the bug to receive notifications about its fix implementation and possible workarounds.

At this moment, it's possible to work around the problem by removing the required fields from your sub-task create screen, so the pop-up will not appear and the selected issue type would be respected and use the required fields for the next status of the sub-task (With validators). We understand this is not a very useful option, so we're currently working to definitely fix it.

Please, let me know if you have any questions.

Perfect - thanks so much for the link (I will vote and watch).  And I appreciate the suggested work-around, but we definitely need to keep our required fields.  So we will eagerly look forward to the fix.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events