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

Why some fileds do not have the Required option

Albert Puigbó

I'm trying to make Epic Link mantadory in field configuration but the action "Required" is not available.

What am I missing?

Accepted answers

Grigory Salnikov_0hffsd

Hi @Albert Puigbó

I do not know the reason behind it yet. But I've found a workaround should you need it:

https://confluence.atlassian.com/jirakb/how-to-make-epic-link-required-on-jira-software-issue-create-screen-815566675.html

All comments

Nic Brough -Adaptavist-

Nothing. The Epic link is deliberately not mandatory, because most places want to allow people to create issues outside Epics

Grigory Salnikov_0hffsd

Hi @Albert Puigbó

I do not know the reason behind it yet. But I've found a workaround should you need it:

https://confluence.atlassian.com/jirakb/how-to-make-epic-link-required-on-jira-software-issue-create-screen-815566675.html

Albert Puigbó

thanks, it worked. But I had to split the workflow for every issue type

Grigory Salnikov_0hffsd

Hey, I'm glad it worked.

Have a nice day

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