how to make epic link required on issue edit

[dan_hersonsky]

the field 'epic link' is locked. It is mandatory on create an issue but not in edit screen.

can i change it ?

[Dave Mathijs]

Hi @dan_hersonsky welcome to the Atlassian Community!

If you made the Epic Link required in the field configuration of a Story/Task issue type, then all newly created issues would have an Epic Link.

Is there any reason why one should remove the epic link again from such an issue?

[dan_hersonsky]

Dave hi

first of all thank you for your time.

second just to make sure that u understand, i want to make 'EPIC LINK' field required also in edit screen for the issue ( story) for 2 major reasons:

1. user can delete the epic link when he is editing a story

2. when i move different kind of issues lets say 'change request' to be 'story', it is not mandatory for the user to specify 'EPIC LINK' as part of the move action ( unlike other fields) 

And as response for what u asked, basically u right, no one should remove the epic link and basically i asked this question based upon what i wrote on #2. 

thx again

[Nic Brough -Adaptavist-]

The mandatory flag in the field configuration makes a field mandatory for the whole lifecycle of the issues - a user will need to fill it on Create, and will not be able to leave it blank during edit or transition.

Mandatory does not mean "has to change on every edit", it just means "can not be left blank, or blanked out"

The "move" action (which is not something you should ever have as part of your standard process) checks for mandatory, amongst other things, against the target project/issue-type.

[dan_hersonsky]

Nic hi 

I understand what u r saying and yet this is how my system acts like ( JIRA 8.5.1 on prem not cloud), she allows you to live EPICLINK blank ( or delete) when editing the issue while it's mandatory when creating one. 

I would more than happy to share it some how with you.

The "move" action ( which i agree that should barely happen) do checks for mandatory.

[Nic Brough -Adaptavist-]

Ok, I was a bit confused because you said "i want to make 'EPIC LINK' field required also in edit"

You can do that really easily - set the field mandatory in the field configuration.

To do "mandatory on create, but not edit", there are a couple of ways to do that, and I do not know which one you might be using:

• you have a validator on the "create" that refuses to let you create the issue without an Epic link
• you have an app like Scriptrunner Behaviours that can make fields mandatory on the front end
• you have some custom javascript that does the same as above

Could you explain what happens if you try to create an issue with a blank epic link?

[dan_hersonsky]

Nic hi 

Again, i can't create issue with blank epic link. It is mandatory on creation. 

After i created' I can edit the issue and delete the epic link and thats what i want to avoid.

[Nic Brough -Adaptavist-]

I'm trying to establish what you have configured that makes it behave that way, not talking about what you're trying to achieve.

Can you explain what happens if you try to create an issue with a blank epic link?  How does it tell you that you need to enter a link?

[dan_hersonsky]

Hi Nic

Yes i can explain. It is really simple i get notification in red under the 'Epic link' field - 'Field Epic link is required'.