creating subtasks without opening it

[Joachim]

Hi all,

wenn creating subtasks in an issue via the +-Button and clicking "create" after adding the summary the subtasks directly opens and I have to again click a create button in the opened mask instead of the subtask just being created directly.

This has changed. Formerly it was possible to create subtask after subtask in an issue  just by adding a summary and clicking create without any subtasks being opened. 

In the subtask mask that shows up all required fields (project, summary, type, reporter) are filled.

I do not know where this change come from in our project. Can anybody help me here?

(I did not change anything that could lead to this behaviour as far as I know, maybe jira has changed something?)

Best regards

Joachim

[Ashish Bijlwan · Accepted solution]

Hi @Joachim 

Welcome to Atlassian Community!

There must be a field which is mandatory and don't have any value/default value.

Kindly check for such field.

Go to Project Settings--> Issues --> Fields and check the Field Configuration applied for Sub-Task and then go through with each field and look for any required field:

If there is any required field then go to  Settings --> Issues --> Custom field and search that field and see if it has any default value or not. Accordingly you can take action on such field. 

Thank you,
Ashish

[Joachim]

Hi Ashish, 

thank you for your fast answer!

I found the cause of this. It is caused by a conditional validation in the workflow that checks for a field to be set when type = epic. 

Thank you for helping me, now I have to find a solution for this.

Best regards

Joachim

[Ashish Bijlwan]

Hi @Joachim 

I believe Sub-task is sharing the same workflow that Epic has. If this is the case then you need to create a separate workflow for Sub-task to resolve this issue.

Thank you,
Ashish

[Joachim]

Hi @Ashish Bijlwan ,

thank you. The problem was not, that the formula was not working properly, it worked perfectly well. This field was only mandatory for Epics.

I tried your formula but your fromula has the same side effect on subtasks...

Still searching for a solution.

Best regards

Joachim

[Joachim]

adding another workflow is not really an option, as this comes with increased maintenance... We do not want to do this, as we had experience with this in the past.

(separate workflows for epics / issues / subtasks)

[Ashish Bijlwan]

Agree with your point that having separate workflow for issue types increases the maintenance. But Jira workflow validators validate issue types on the create transition that is why the clicking on create button for Sub-task open the create screen pop up. 

Another option is that, you can create a separate Field configuration for Epic and with in the Field Configuration make the field Epic Type required and remove the validator from the workflow.

[Joachim]

would be an idea. I personally think that all these field configs are not the best part in jira. (unneccessary complex or intransparent in my opinion, or maybe I just do not like it)

I like to keep it as simple as possible. But if my colleague has no better idea, I maybe solve it this way.

[Joachim]

we solved it with the 2nd workflow. seemed to be the most straightforward solution that should haves other positive effects as well. we think we are more mature now, so that it should not be more maintenance effort.

thanks for helping me! @Ashish Bijlwan 

[Ashish Bijlwan]

Glad to know that.

Please accept the answer if you found my suggestion helpful in anyway.

Thank you,
Ashish