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; } } }

Subtask - Required field error message

Karrie Dash_ovl3wg

Is anyone else having the following issue?

We require all tickets to have a COMPONENT selected.

When It Doesn't Work

When creating a subtask while viewing the issue in a pop-up module the following error message sometimes appears after I type the task name and click on CREATE.

This does not happen for all tickets. Only some tickets, even if they are the same issue type.

Example: Viewing the parent task from a board.

When It Works

If I go directly to the ticket link (ex: https://XYZ.atlassian.net/browse/IO-36), I can create a sub-task ticket.

When I enter a ticket name and click on CREATE, the Create Issue screen appears (as expected)

Accepted answers

All comments

Rilwan Ahmed

Hi @Karrie Dash ,

Welcome to the community !!

This error is displayed when the component field is made required in field configuration that is configured to the project. The Jira admins needs to update the field configuration and make component field as Optional

Karrie Dash_ovl3wg

Except that I can create a sub-task as expected within the ticket if I go directly to the ticket link. This error sometimes occur when I have the ticket open as a pop-up module.

Lígia Zanchet

Hello Karrie,
Thank you for reaching out with your question.
When you open the issue from the project board, a pop-up window for the parent issue is created. If the subtask requires a component, you need to open the issue creation screen to fill in that field.
However, because you already have a pop-up open for the parent issue, it's not possible to have a second pop-up open for the subtask creation screen.
For that reason, you see the warning message, and the issue is not created.
The workaround, as you've already mentioned, is to go to the parent issue in order to have the pop-up for the subtask creation screen.
I hope this clarifies your question.

Karrie Dash_ovl3wg

Hi Ligia,

In some tickets, I am able to successfully view the Create Issue screen while the parent issue is opened in a pop-up window.

Bill Kershner

Hi @Lígia Zanchet , @Karrie Dash, and @Rilwan Ahmed,

We have Contributors in our org that are experiencing the same problem. The navigation sequence below is what is problematic for our particular workflow:

1. Contributor updates Story A by adding a subtask. Dialog "pops up," required field entered ok. subtask is saved ok.

2. Contributor navigates to Story B and attempts to add a subtask. Dialog does not "pop up" and addition of subtask fails.

3. Contributor navigates to Story C and attempts to add a subtask. Dialog does not "pop up" and addition of subtask fails.

4. All subsequent subtask addition attempts fail.... until workaround is used.

Our issue is that the Workaround interrupts the logical flow of our Contributors' work making them go to the Parent item in order to get the Dialog to correctly appear. The workaround also opens new tabs in the browser which the Contributor would prefer not to have to close out/clean up after processing all Stories in "workaround mode."

We hope there will be a longer-term fix to this issue forthcoming soon.

Best Regards,
@Bill Kershner

Lígia Zanchet

Hi, @Bill Kershner and @Karrie Dash. Thank you for the additional information.
That seems like something we might need to revert to a support ticket for additional investigation.
Is there any difference between how the field is required? For example workflow requirements vs field configuration?
I can transfer this question into a regular ticket if you prefer

Karrie Dash_ovl3wg

Hi @Lígia Zanchet

Yes, if you could transfer t his into a regular ticket, that would be great!

I have not set up the field to be required during a workflow transition, but I will test that out this week and will report back.

Lígia Zanchet

Hey @Karrie Dash
I submitted the ticket on your behalf, you should received the notification directly in your inbox

Thanks

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