Custom subtask changes when adding in a new subtask.

[Geoffrey Melle]

I created a new type of subtask called a "Bug Sub-task" because we wanted to connect our bugs to stories that show them as required to getting that story complete. When I click the "+" symbol to add a subtask within a story, a drop-down appears to let me select "Sub Task" or "Bug Sub Task". I then choose "Bug Sub Task", enter in the summary, hit enter which opens up the window to add the remaining fields to the sub task, but Jira keeps defaulting the issue type to "Sub Task" in the pop up window.

I can change the subtask type back to "Bug Sub Task" in the pop up window but why isn't it keeping my selection from the previous window? Is this a bug or do I have a configuration/setting somewhere that is causing this?

Thanks for your help. 

[Petter Gonçalves]

Hello @Geoffrey Melle

Welcome to Atlassian Community.

Indeed, the behavior that you described where Jira resets the sub-task type to the default in the pop-up window is a known bug with the application. In fact, the pop-up screen is only displayed when you have any required fields in your sub-tasks, so we created the following bug report with our development team to get it fixed:

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 increase its priority and also receive notifications about its fix implementation.

For now, the only workaround available for this bug would be to make optional all the required fields of your sub-task, so the pop-up screen will not open and the issue will be created with the initial sub-task type you selected.

Let us know if you have any questions.