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

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

Guy Incognito_79x5fx

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

Accepted answers

Ram Kumar Aravindakshan _Adaptavist_

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 (issueContext.issueType.name 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

All comments

Ram Kumar Aravindakshan _Adaptavist_

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 (issueContext.issueType.name 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

Guy Incognito_79x5fx

@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

Guy Incognito_79x5fx

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

scriptrunner

jira

jira-server

behaviours