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

Jira is forcing a required field which is not used on a screen

Gil_2dvf2c

Hi.

I'm trying to setup a new screen and field schemes for a project.

I created a screen per issue type.

When I create an Epic, I use the Create Epic screen and Jira is asking me to fill in required fields such as Components and Fix versions. While these fields are configured to be required, they are not configured as part of this screen.

For example, I only need Fix Version and Component on a Story, not an Epic.

I think I'm missing something, or I've done a mistake. Why Jira asks for a required field which is not part of the screen?

Accepted answers

Ollie Guan

Hi @Gil,

Yes, as long as the field scheme is set to be required, even if you choose not to display this field in the screen scheme, the system will still make this limitation. It is recommended that you configure different field schemes for different IssueTypes.

All comments

Ollie Guan

Hi @Gil,

Vishnukumar Vasudevan

Can you check the field scheme used by this issue type and make following changes ?

1. Either make these fields optional for above mentioned issue type

2. or Add these mandatory fields to create screen.

Gil_2dvf2c

That doesn't make any sense.

What's the logic behind triggering a condition that is not part of the issue type screen?

For an Epic issue type, the screen doesn't require Fix Version or Component.

Ollie Guan

Hi @Gil,

You can refer to @Vishnukumar Vasudevan's suggestion.The required fields will generally appear in the following configuration.

1. Set as required in the field scheme
2. Limit the required attributes in the workflow configuration

If your Epic does not need to display Fix Version and Component, please set these 2 fields to optional in the field scheme configuration.You can configure differentiated field schemes for different IssueTypes.

https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html

Gil_2dvf2c

I ended up creating field schemes per issue type. So the Epic create screen won't prompt for a required field such as Fix Version, but it will require it Story create screen.

Now I need to see how can I safely switch the new workflows, screens and field configuration to an existing project

Thanks.

Gil_2dvf2c

Hi @Vishnukumar Vasudevan I didn't want to make the fields optional because they were shared across all issue types.

I ended up creating a separate field config per issue type.

thank you!

Vishnukumar Vasudevan

Good to know that you could resolve the issue.

Charlie Sobel

I'm having a similar problem. Most of the answers I've seen for this issue are about Workflow transitions, but all I'm doing is creating an Issue. We're using Jira 8.8.

When trying to create an Epic, the user gets an error that Custom fields 2 and 3 are required.

When trying to create a Story, the user gets an error that Custom field 1 is required.

@Gil said he wound up creating separate field configs per issue type, but I don't understand why that would be needed.

Here is my current set up: I have 3 Screen Schemes, 1 Issue Type Screen Scheme, and 1 Field Configuration Scheme.

Epic Screen - Epic Issue Type - Default for unmapped operations - Custom field 1 is required - Custom fields 2 and 3 do not appear
Create Issue screen - Default for unmapped Issue Types - Create operation and Default - Custom fields 2 and 3 are required - Custom field 1 does not appear
Edit Issue screen - Default for unmapped Issue Types - Edit operation - Custom fields 2 and 3 are required - Custom field 1 does not appear
View Issue screen - Default for unmapped Issue Types - View operation - Custom fields 2 and 3 are required - Custom field 1 does not appear
Sub-Task screen - Sub-Task Issue Type - Default for unmapped operations - Custom fields 2 and 3 are required - Custom field 1 does not appear

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