Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Epics text missing in filters

Heidi Maul Jars July 17, 2019

Hi

When I use filters - any filter -  I always need the Epics titles for each Story etc. So far I have not been able to add this, only the Epics number. I have tried to add all sorts of attributes, but no luck.

I'm not a programmer, so this is not really a competence of mine, but I think I have tried all sorts of combinations.

I need the Epics title in order to easily investigate how much time has been spent on any give Epic.

I hope someone can tell me how to do this, as I'm getting a bit desperate...

Br

Heidi Maul Jars

 

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 22, 2019

Hello Heidi,

I understand that you would like to return the Epic Summary (Title) as a column when running JQL Searches for Stories in your JIRA application. Is it correct? Or are you trying to return stories related to an Epic that has a specific summary?

Unfortunately, the Summary of an Epic can not be returned in the Column of JIRA issue navigator, however, based on the requirement that you would like to easily investigate how much time has been spent on any give Epic, I would recommend you to return the Epic Link field, which provides you with the Epic Name related to that returned Story which is a more reliable information.

Better explaining, the summary of an Epic is something that can be easily changed in the issue view since it has more visibility, while the Epic name is the field used to better identify the Epic in an intuitive way, which can be restricted from being edited if needed.

To display the Epic name of your Stories:

- Navigate to your issue navigator > Search for the Stories you want

- Using the List view, select the fields you want to display together with the Epic Link

Screen Shot 2019-07-22 at 18.36.46.png

If the steps above are not what you are looking for, please feel free to provide us with more details and screenshots explaining your final goal.

Heidi Maul Jars July 23, 2019

Hello Petter

Thank you for your reply. Unfortunately I can't seem to make it work, as I hope you can see from this screen shot. I have tried this setup several times, but it has never worked. From what you see here, can you tell if I set it up correctly?

Br

Heidi

Scrum project - missing the Epic subject.png

Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 24, 2019

Hello Heidi,

Thank you for your screenshot.

I have two questions about the issues you are displaying there:

1 - Are the issues linked to a valid Epic?

2 - Are the issues related to a Next-gen project?

Next-gen projects use a different Epic relation than Classic projects, where it does not have the default Epic fields (Epic Name, Epic Link, etc). We have a feature request about this here:

Next Gen project - ability to add Epic link when creating an issue

If you are using Next-gen Epics, the only workarounds available to display it in the issue navigator page would be by:

1 - Transfer your issues to a Classic project. Note that the Epic relation would need to be configured again

2 - Add a new custom field to the Stories informing which is the Epic they are related to

Additionally, feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

Let me know if this is the scenario you are having, Heidi.

Heidi Maul Jars July 26, 2019

Hello Petter

Thank you for the input! You are right it is a Next Generation project. I was not aware that it was a "lighter" version of Jira, I just liked the interface better. Had I known that it was a lighter version, I would not have used it to begin with.

I'm however somewhat dissapointed that I have to merge it into a Classic project. As I said I like the feel that the Next Generation project has, and it is just less .. cluttered and more userfriendly. But I need the functions that the Classic project has. 

Do you know if there are any plans for the Next Generation project to be updated to with these functions? As I see it, it has a lot of potential, and I would love to be able to keep on using it.

Br

Heidi

Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 26, 2019

Hello Heidi,

you are welcome. Thank you for your detailed answer.

We completely understand your point and we're sorry to hear that Next-gen projects do not have all the functionalities you need, although you liked its design.

Answering your question, we are currently working to implement this functionality in next-gen soon. Although we have some feature requests about the Epic functionality on Next-gen, this would be the correct one for the improvement you are looking for:

As a user, I'd like to be able to use JQL for Epic Link for Next-Gen project epics

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

As you can see in Nathan's last comment, we are in progress to implement a way to display the Epic name in the Parent or in the Epic Link column, so we hope Next-gen can fulfill your need anytime soon.

For now, if you decide to start using the Classic template of JIRA, you can optionally follow the instructions in the documentation below to move your next-gen issues to a Classic project:

Migrate between next-gen and classic projects

Let me know if you still have any questions.

Like Heidi Maul Jars likes this
Heidi Maul Jars July 28, 2019

Hi Petter 

Thank you for your very prompt reply. It was very useful. My only question now is: when do you anticipate this feature: As a user, I'd like to be able to use JQL for Epic Link for Next-Gen project epics will be implemented?

It says In Progress, but I need to know if I should go ahead and migrate into a classic project, or wait it out. I can wait a few weeks, max a month, and if not I will need to start migrating a.s.a.p. I have already started migrating closed issues over, but as I will need to do it in batches to add the right Epic to each issue, it takes a lot of time.

TIA :)

/Heidi

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events