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

Field configuration scheme question

Rumceisz

Hi All,

if we apply a field configuration scheme where custom field "A" is set to required but we didn't configure the field to project "X" then it won't require when creating/updating an issue?

So the custom field "A" doesn't exist in project "X" but the project's field scheme has this required field.

Thanks,

Rumi

Accepted answers

Peter Van de Voorde

Hi Rumi,

This will cause an issue because the field is required even when it's not available on any screen in your project.

Best regards,

Peter

All comments

Peter Van de Voorde

Hi Rumi,

This will cause an issue because the field is required even when it's not available on any screen in your project.

Best regards,

Peter

Rumceisz

Hi Peter,

no, you are talking about the case when the custom field is configured to the project (like any projects) but is not added to any screen. This causes an issue.

In our case it just turned out that a custom field was set as required on a field scheme and the field scheme is applied by 200 projects. But the custom field is only configured to 11 projects. We wondered that none of the users of the 200 projects ever complained about this custom field blocking their issue creation.

Based on this, if I don't add the custom field to the project (not screen, but project!) then feel free to make the field required or not?

Thanks,

Rumi

Peter Van de Voorde

Hi Rumi,

It seems you are right, I didn't think about the fact the you can use custom fields only in certain contexts and how this would impact your field configuration.

So feel free to make the field required

Best regards,

Peter

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration