nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

creating subtasks without opening it

Joachim_t9mbr6

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

Accepted answers

Ashish Bijlwan_zogaqs

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

All comments

Ashish Bijlwan_zogaqs

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_t9mbr6

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_zogaqs

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_t9mbr6

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud