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!
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?
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 :
We've tried the unlock/lock procedure, but a JIRA restart will 'un-require' the Epic Link field. Another user asked about this here, but no answers at this point.
Has anybody solved this? Enforcing this on workflow doesn't work for us, because it doesn't cover the case where somebody 'moves' a Bug or Task to a Story. If we require Epic Link on Story only (as a validator on create transition), then people can get around this by creating as a Bug or Task, then moving the issue to a Story. The issue is already created so the validator doesn't stop it.
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.
@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?
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.
Hmm. I have tried to set this up now without success. It could be something with my S-JQL query, but JIRA does not complain when I set up the validator. Setup is as follows: Epic Link must be set when creating issue. Structure: The default structure of the issue's project S-JQL Query: not ["Epic Link" = NULL] If the Issue Is Not Added to the Structure: Block transition Run as User: Project lead This results in it being impossible to create issues (regardless of if Epic Link is empty of populated). The error message is as follows: Workflow transition was blocked by the Structure Validator. An internal error occurred.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs