Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,257,417
Community Members
 
Community Events
164
Community Groups

Issue Filter is not showing the Epic Name

Edited

We have multiple epics under a project and we are not able to see or filter our Issues based on Epics they are tied to.  Why are the Epic Names not showing in the Issues Filter?

All of the issues are "Child issues" and showing on the Board and can be filtered by Epic name there, but in the issue filter, the column is just blank.  

3 answers

1 accepted

4 votes
Answer accepted
Jack Brickey Community Leader Jan 08, 2019

i'm guessing you are using a Next-gen project which does not support the Epic Name field yet. 

Yes it is Next Gen.  I guess we have to add a label to each issue so we can filter and sort.  Thanks

For those looking for how to show the epic name, the parent field can be used to show the assigned epic.

Like # people like this

I'm unable to create a filter based on the epic name on next-gen. The option is there, but epics don't show up

Expecting us to use hacks doing a lot of research is not at all fair

Jack Brickey Community Leader Feb 02, 2021

Hi Midhun, NG doesn’t support Epic Name.

Thank you @Paul Argue you solved my issue :)

Is there a plan for NG to support epic names?

Like Simon Ashby likes this

Go to Columns and select Parent to see Epic for each issue. 

 

Parent.png

 

Hope this helps.

Go to Columns option near Search button on filter screen section and then choose an Epic Link value from the list like on attached screen.

screen.jpg

thanks Michael -- it added another column, but still shows up as blank.  Assuming it is the issue with Next Gen,

Like # people like this
Jack Brickey Community Leader Jan 08, 2019

yes it is because u r on NG.

Like # people like this

After adding the Column for 'EPIC LInk' on the Issue Search, the result just shows blank column. Is this a feature in the New Gen JIRA Project? Strange because it seems to have broken a simple and very important feature of being able to view the EPIC Link in the issue search. Is there a way to change a New Gen type of project to the older one?

Like Midhun Tej likes this
Jack Brickey Community Leader Mar 12, 2019

@Harneet Singh , correct that is what this thread is saying. There is an article that explains how to change from NG to Classic but I don’t have it at my fingertips. You can search the community and find other threads that will point you to it. Basically it is a ‘simple’ matter of creating a Classic project and bulk moving issues.

Like John Scott _Concord_ likes this

Any ETA for this capability in the NG projects?

Like # people like this

I have the same doubt, any ETA?

Like Chris likes this
Jack Brickey Community Leader Apr 12, 2019

Just coming off Summit. There was plenty of talk and focus on NG so clearly NG is a major initiative for the company. With that said, there is no public commitment to this  AFAIK. I would highly recommend using the feedback link if you have not already done so.

Like Jean-Marc Fritsch likes this

In my project is not an option to go from NG to Classic (due to business decisions), thank you anyway.

Disappointing - Not easy to switch between Classic and NextGen either - I wonder why is the onus on us to search for and switch! Don't understand why good features in classic were removed in next-gen

Jack Brickey Community Leader Feb 02, 2021

NG is a ground up development so it wasn’t removed. The relationship between Epic and its children is simply different.

Having a different relationship is all fine as long as we can search the EPICs in NG, else the existence of the relationship is not really serving the purpose completely.

From development perspective it seems that the backend table for EPICs in the older version and NG are different and maybe even the DBs are different, which is why the results are independent of each other even though the column names are the same. This should've been thought of at the time of designing the NG itself, much before development was initiated.

When you upgrade any product, it is of utmost importance that the existing customers using the older versions are able to smoothly able to transition to the newer version without any adversities. If there is a feasibility issue found in doing that, it is more like moving to a totally different product than upgrading the older system, which is what you have termed the new version as 'Next Gen'.

Jack Brickey Community Leader Feb 03, 2021

@Harneet Singh , I would suggest you provide this feedback to Atlassian via the feedback links in you instance.

Thanks for your guidance Jack!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

1,497 views 11 22
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you