Required field not appear

[Oshadhi Vindhyani]

Hi, 

I created a required field for issue. It appear when I create using "Create" Issue. But when I'm creating issues under epic as a child issue it is not ask for required. I want that selection every time I created issue. How do I do that? 

Background: I have 2 boards for each project to work 2 different team. So I use a required selection when issue creating and based on that value I filter issues for boards. Without that field value  issues not display on board. 

Ex: Board A & B , Project X , Required field value = A or B  
Filter for board A: 

project = TP AND issuetype in(standardIssueTypes(), subTaskIssueTypes()) AND cf[10052] IN ('Dev') ORDER BY updated DESC 

If you have better solution that this. Please let me know. Thank you. 

Jira cloud, Standard package, Admin access 

[Megha Rajanna]

HI @Oshadhi Vindhyani 

To ensure that the required field is prompted for every issue creation, including when creating child issues under an epic, you need to configure the field at the project level and ensure it's set as required for all issue types within that project. Firstly, navigate to your project settings and select "Fields" from the sidebar menu. Then find the custom field created for the required selection and click on "Configure" next to it. Ensure that the field is associated with all necessary screens for issue creation and make sure it's marked as required. Additionally, update field configuration settings by selecting the relevant project and ensuring that the field is marked as required for all relevant issue types (e.g., Story, Task, Sub-task).

THANK YOU

[Ignacio Aredez GenAI Expert]

To ensure your required field appears for all issues, including child issues under an epic, and to refine your board filters in Jira Cloud, follow these streamlined steps:

Making the Required Field Appear
Verify Field Configuration: Check that your required field is set as "Required" in the field configuration for all relevant issue types, including epics and their child issues.

Adjust Screen Schemes: Ensure the screen used for creating issues includes your required field. Screens control which fields appear during issue creation.

Refining Board Filters
Your current approach of filtering issues for boards based on a custom field value is effective. Ensure that the filter for Board B mirrors the filter for Board A, adjusting only for the specific team value.

Simplifications and Improvements
Use Automation: Automate the setting of your required field based on criteria like issue creator or issue type to reduce manual entry errors.
Consider Quick Filters: If feasible, combine boards and use quick filters to dynamically filter issues by team, reducing the number of boards you manage.
Educate Your Team: Ensure all team members understand the importance of correctly setting the required field to ensure issues display on the correct board.

By ensuring your configurations are correct and considering automation and education for your team, you can streamline your process and ensure that issues always appear on the intended board.