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

How do I fix epic(s) from appearing as unlabelled?

tina.raftopoulos

I've created a Jira Board Company wide and imported project(s) that are team board into the company wide board. However when I create a new Epic, the epic is displayed in the company wide board as "unlabelled-<projectname>-<projectnumber>" and the issues displayed is always 0. Therefore I cannot use the Jira Company wide board to sort through the appropriate issues and its frustrating.

image - shows the unlabelled EPIC with 0 issues, but there is 1 issue, when you select LUI-183 and open it outside into its own board (team managed) it displays.

See image 2.

Screen Shot 2021-05-14 at 1.15.34 pm.png

Accepted answers

All comments

Linda Milne_Togetha Group_

It looks like the field "Epic Name" has the value unlabelled-LUI-183. I have had issues with this in the past - the Epic Name is not required for Team Managed, but is needed for Company Managed. So you will need to populate that field with the value you want. You (or your jira admin) may need to make this field available for you to use.

tina.raftopoulos

@Linda Milne_Togetha Group_ thanks for responding. it displays directly in that board without any issues, so unsure how do you make it "available to use" is there something specific we would need to enable?

The other issue is even if I manually populate it which would be a pain, I still cannot see how many issues attached, as it says "0", despite there being multiple issues attached to an epic.

Linda Milne_Togetha Group_

If I'm understanding your screen shots - you are using the epics from a team managed project? If you look at the equivalent in a company managed project you have two fields that are used:

And this will translate to:

epic backlog view.jpg

If you try to view a team managed epic in a company managed context you will not see the Epic Name field populated. You need to make the "Epic Name" field available in your team managed project - your jira admin should be able to help you with this.

Linda Milne_Togetha Group_

Correction. Looks like you cant add that field to a team managed project. So you will need to find another way - can you migrate it to a company managed project?

tina.raftopoulos

@Linda Milne_Togetha Group_ I am unsure if I migrate it to company managed, can one company manage, use filters to grab in other projects that are also company managed?

Is there an easy way to migrate from one to the other? Any info over that would be amazing.

Linda Milne_Togetha Group_

You can migrate between team managed and company managed. Check out:

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

I suggest if you want to do this you create a test project, that looks like your team managed project, add the same issues with fields as configured in your current project, and try copying it into a test company managed project. Make sure you know what things need to be configured in the new project and how the process will work before you do the move.

tina.raftopoulos

yep, I was thinking the same thing to do a test first. it's so annoying though because basically it all works except for the epics, which causes issue for when grooming backlog from the combined company board. it's a shame Jira doesn't fix this issue, but thanks so much for sending this info through.

Linda Milne_Togetha Group_

Did you see me comment above? Did you try searching for Epic name in the previously created fields, search field in the bottom right hand corner?

Did that return anything?

Daniel Ebers

Hi @tina.raftopoulos

adding to the great information Linda already gave to help you I found a bug which documents this behaviour:

Adding a next-gen Project via Filters to the Classic Board shows the Epics of the next-gen as unlabelled Issuekey
https://jira.atlassian.com/browse/JSWCLOUD-17761

At the time of writing these lines the bug has 28 votes and 36 watchers.

Please consider adding yourself to the bug mentioned in order to signalize this bug is impacting your work and of importance to your team.

From a personal view: because the bug is not gaining traction as of now I'd also suggest the steps Linda mentioned.

Regards,
Daniel

tina.raftopoulos

thanks @Daniel Ebers I have switched all my boards to company wide boards instead of team and it fixes the problem.

Judith Vorster

Hi, I am battling with the same problem. I just want to check that I understand the workaround correctly?

Firstly, I should ensure that the project in which I'm going to create my Epics, is a company managed project and not a team managed project. The project JIRA Admin will have to allow me to change the Epic Name setting on the project Epics.

Then, I can create Epics in that project. Each time I create an Epic, I have to and manually update the Epic Name to match the Epic subject line.

I can then add JIRAs from multiple projects to that Epic - JIRAs belonging to both team- or company managed projects (as long as the Epic belongs to a company managed project).

Is that correct?

Daniel Ebers

Hi @Judith Vorster

Firstly, I should ensure that the project in which I'm going to create my Epics, is a company managed project and not a team managed project.

...yes, this seems to be the most relevant part.

Then, I can create Epics in that project. Each time I create an Epic, I have to and manually update the Epic Name to match the Epic subject line.

That is a good idea, however, it seems to be optional. For the bug it seems to have no specific relevance.

I can then add JIRAs from multiple projects to that Epic - JIRAs belonging to both team- or company managed projects (as long as the Epic belongs to a company managed project).

This is something that was not tested right now on my side, but you could double check and confirm. Indeed important it seems to be Epics reside in a Company Managed Project.

Regards,
Daniel

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

epic

label