Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Can I completely remove Epic Link field (including validation error) from a screen using behaviours?


Hi all,

I have a project where I use the same screen for stories and epics.

I wrote a Scriptrunner behaviour to hide the "Epic Link" custom field from the screen, when the current issue is an Epic.

The field is now hidden, but the validation error "An epic cannot have another epic linked to it." is still visible, together with the helper text "Choose an epic to assign this issue to.", and the field name "Epic Link"


Is there a way to remove these texts from the screen?

Thanks in advance

2 answers

1 accepted

0 votes
Answer accepted
Ram Kumar Aravindakshan _Adaptavist_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 31, 2023 • edited

Hi @Guy Incognito

I have run a basic Server-Side Behaviour test for the Epic Link in my environment, and I can hide the Epic Link field for all issue types except for the Epic issue type.

Below is the sample code that I have tested with:-

def epicLink = getFieldById(fieldChanged)

if ( in ['Story', 'Task', 'Bug', 'Epic'] ) {
epicLink.hidden = true

Below is a screenshot of my Behaviour configuration:-



This may be a Bug. I suggest creating a ticket on the Adaptavist Support Channel for further investigation.

Thank you and Kind regards,


@Ram Kumar Aravindakshan _Adaptavist_, I did as you suggested  and the answer was "It's not possible to hide those errors", probably they're hard-coded in the core of Jira.

Never mind, I'll explain this to the users.

Hopefully the new way of setting parent relationship developed by Atlassian, is going to solve this problem.

I'll accept your answer, as I learnt by it that I can actually raise a bug request at Adaptavist. Thanks :)

I slightly changed the title of this ticket in the hope that other users locate it when facing the same issue

Suggest an answer

Log in or Sign up to answer