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

Customize a "epic-link" field

Eran Ben Ari

Following Atlassian decision to replace the single most important field (epic-link) with a horrible one (parent field), can we customize an epic-link-like field ourselves?

can you fix the issue of the parent field not showing many epic in the suggested results list?

Accepted answers

Trudy P Claspill

Hello @Eran Ben Ari

Can you expand more on the issue you are facing?

the issue of the parent field not showing many epic in the suggested results list?

I assume that you are working with issues in a Company Managed project, as the Parent field can't be added to the Context section of issues in a Team Managed project.

What issues are you expecting to see in that list that you are not seeing?

Are you trying to type some information into the field to get a subset of Epic issues that match?

All comments

Trudy P Claspill

Hello @Eran Ben Ari

Can you expand more on the issue you are facing?

the issue of the parent field not showing many epic in the suggested results list?

I assume that you are working with issues in a Company Managed project, as the Parent field can't be added to the Context section of issues in a Team Managed project.

What issues are you expecting to see in that list that you are not seeing?

Are you trying to type some information into the field to get a subset of Epic issues that match?

Eran Ben Ari

Hi Trudy, thanks for replying.

Epic-link, when used in queries, gave a precise list of epics corresponding to the text given by the user:

Epic link = "abc

Now, a suggestions list appears with relevant epics.

Now, all sorts of results appear, and the most desirable ones (actual *epics*) are many times missing.

Further more, the list cannot be scrolled or used to fetch more results.

Trudy P Claspill

Hello @Eran Ben Ari

So, you are talking about the use of the Parent field in filters, not the use of the Parent field in an issue view, correct?

I have the same experience you describe when using the Parent field in filters. Because it is used to denote Epics as parents of standard level issues, and to denote standard level issues as parents of subtask level issues, both Epic and standard level issues are shown as possible matches.

When using the field in an issue view, the matches are relevant to the type of issue you are viewing, showing only matches from the Issue Level Hierarchy that could be parents of the issue being viewed.

I'm afraid I don't have a workaround suggestion for the filtering.

If you haven't already you might want to look through the comments on the community article about the change to see if that has been asked/answered, and consider posting your question as a comment there.

https://community.atlassian.com/t5/Jira-Software-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758

Eran Ben Ari

Thanks for this, I will.

Meanwhile, it seems "epic-link" became available again!

hopefully, for good.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud