Is it possible to require an Epic link on a Story?

[Chris Flynn]

Does anyone know how/if it is possible to make the Epic Link a required field on Story issue types (not all issue types)? Also if it is possible to make it required on Stories in a specific list of Projects?

[Andy Heinzer]

There are two different approaches you could use in Jira Server to make this work:

1. The first is by modifying the workflow.
2. The other is by using SQL to unlock this system field (at which point you can make it required in the field configuration in use).

Method #1 is explained in the KB : How to make Epic Link required on JIRA Software issue create screen

I would suggest this method because it doesn't require you to use SQL modifications.  The drawback here is that by using this validator method, end users might not be aware that this field is required.

In method #2, you can unlock a locked Jira Software Field first.  When you unlock a field via this method, Jira is running when this is done, and suddenly when you look at the field configuration of that field, you can make it required by the field configuration in Jira.  If you choose this method, I would recommend first creating a new field configuration to start.  This way you could specifically assign this field configuration only to Story issues in that specific project.  That way this field would not be required for all issues in all projects or all story issue types in other projects.

I hope this helps,

Andy

[Chris Flynn]

@Andy Heinzer -- thank you very much for your help. I will take a look at these solutions this week and let you know how it goes.

Thanks for the help!