Subtask - Required field error message
Asked by Karrie Dash:

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.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/332622iAD649536F4608640/image-size/large?v=v2&px=999 "image.png")

++**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)

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/332621i08A92D467A2B183B/image-size/large?v=v2&px=999 "image.png")

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/332620i903F4220D8DADE6A/image-size/large?v=v2&px=999 "image.png")


Answers:
author: Rilwan Ahmed
body: Hi [@Karrie Dash](/t5/user/viewprofilepage/user-id/5515851) ,

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**

comments: author: Karrie Dash
body: 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.


author: L?gia Zanchet
body: Hi, [@Bill Kershner](/t5/user/viewprofilepage/user-id/4335238) and [@Karrie Dash](/t5/user/viewprofilepage/user-id/588174). 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

comments: author: Karrie Dash
body: Hi [@L?gia Zanchet](/t5/user/viewprofilepage/user-id/4830848)

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.


author: L?gia Zanchet
body: Hey [@Karrie Dash](/t5/user/viewprofilepage/user-id/5515851)   
I submitted the ticket on your behalf, you should received the notification directly in your inbox :)  

Thanks


author: L?gia Zanchet
body: 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.   

comments: author: Karrie Dash
body: 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.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/332812iA7540DEE61C3D56F/image-size/large?v=v2&px=999 "image.png")


author: Bill Kershner
body: Hi [@L?gia Zanchet](/t5/user/viewprofilepage/user-id/4830848) , [@Karrie Dash](/t5/user/viewprofilepage/user-id/5515851), and [@Rilwan Ahmed](/t5/user/viewprofilepage/user-id/716861),

<br />

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.

<br />

Best Regards,   
[@Bill Kershner](/t5/user/viewprofilepage/user-id/4335238)


Tags: cloud

jira-cloud