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

How to require Epic Link on an issue?

Adam Beckerman1

Epic Link is locked, presumably because it's an internal field to Jira. When we create a field configuration scheme within our project, we are unable to set it to required -- something we are trying to do for control purposes within this project. I have not found any answers/articles/help to indicate how we can require Epic Link to exist on all issue types within our project.

Please let me know how we can do this...

Thanks in advance!

Accepted answers

All comments

AhmadDanial

Hey there, Adam.

Have you tried to unlock the Epic Link field (https://confluence.atlassian.com/display/GHKB/How+to+unlock+a+Locked+field) and make it Required in the field configuration that you want it to be?

Warm regards,

Danial

Adam Beckerman1

Hi Danial, thanks for your reply! Saw that, but we really didn't want to have to go that route. Is that the only feasible path?

Tyler Brandon

How do we run the SQL statements described by Danial? Please provide details.

Thanks.

unknown

Make the Epic Link a required field in the workflow's Create step.

If you make the field required in the configuration scheme, then you'll need to enter an Epic Link when you need to edit some old Stories. You probably will not want to enter any Epic to an obsolete Story.

The only problem with this: the read asterisk will not appear next to the field name.

Try it out.

JamieY

Is this workaround good for 6.4/cloud based installs? I'm looking at the Create transition, but I have no options under Validators or Post Functions that would essentially say, "do not create until Epic Link exists."

Matylda Kozłowska-Igła

@Laszlo Kremer I thought of the same idea as you suggested (validator in workflow), but there is still a problem. If user choose an Epic which status is closed, JIRA accepts the value, but don't saves it in created item. It seems that linking item to an Epic is the same thing to editing the Epic, but users don't have a permission to do it (which is intended). This way users still can create issues with empty epic link and don't even know about that. Do you have any ideas, how to solve this situation?

unknown

I'm not sure it's feasible, but I'd go for script validation, and examine the status of the linked Epic, and fail the validation. I don't have code for this, that's just an idea. The other thing: I'd keep the closed Epics editable, not to prevent creating the epic link. It's better to have 2 stories that have closed epics linked (which can be monitored by query subscriptions), than have 30 stories where the creator only thinks that the Epic link is set but eventually not saved. To be honest, the "closed ticket is not editable" workflow setting causes more user uncertainty and therefore more JIRA support than leaving it editable, and showing users the history tab. It is as counter-productive as the mandatory fields - most tickets with mandatory fields are filled with a dot or the first select item.

Corentin Méhat

You can either connect directly to your database or use a plugin that allows you to run SQL directly from JIRA. You should use the first method and apply the following steps :

In any case, backup your db before doing anything at the DB level
stop JIRA
run your sql
start JIRA

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