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

Epic link optional for story

Aswathi D

Hi ,

I need to make " epic link " as optional to the issuetype story ( currently it is mandatory)

I checked the field configuration and noticed that it is locked field ..so i unlocked the field from database to make it optional

But even after it is optional in the configuration..I can see that under created issue it is mandatory..may I know the reason why it is like that ?

Accepted answers

Hamza Chundrigar

Hi @Aswathi D

Can you check if there’s a field required validator in your workflow that’s associated to the Epic issue type.

Best,

Hamza

All comments

Hamza Chundrigar

Hi @Aswathi D

Can you check if there’s a field required validator in your workflow that’s associated to the Epic issue type.

Best,

Hamza

Nic Brough -Adaptavist-

>I checked the field configuration and noticed that it is locked field ..so i unlocked the field from database to make it optional

Ouch. I would want to go kick the last admin who unlocked it and made it mandatory, they should not have done that. After you corrected that failure, did you re-lock the field?

Also, did you have Jira offline when you unlocked (and re-locked) the field in the database? If not, then you may have lost all the changes you made.

How does it show as "mandatory"? Is there the * showing? Or does it just complain when you try to proceed through an edit and/or transition, and/or create with an empty Epic-Link?

Trudy P Claspill

Hello @Aswathi D

The fact that a field is Locked does not necessarily make it Mandatory. Locked fields are ones for which the configuration of the the individual field (like the field name, description, or search template) cannot be changed through the Custom Fields screen.

In a Field Configuration, if a Locked field is also mandatory it would show "Required" and "Locked" next to the field name. You should see that for the "Epic Name" field in a Field Configuration.

You should never unlock a Locked field. If you think you need to unlock a Locked field you should contact Atlassian Support first or reach out to this community to ask about the problem you are trying to solve.

As @Nic Brough -Adaptavist- described with his questions, what first needs to be understood is how the field was made mandatory.

Aswathi D

Hi @Hamza Chundrigar ,

Yes , It's made by workflow validator .

I missed that part ..thank you so much

Aswathi D

Thanks for your response, it was made via workflow validator

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server