Next Gen Board Epic Link Label Missing

[Hayden Curry]

I am using a next gen project and have encountered a strange scenario whereby:

- I add child stories to an Epic
- When I go to the backlog some epic link labels are visible against their stories and others are not (see picture)

Some extra information:

- It seems either all stories within an epic are effected and do not display the epic link label or all stories within the epic are fine.
- I added an "At Risk" status to my board which some stories and Epics sit in.

Let me provide further examples:

1. I created a new epic and added a story as you can see it displays correctly:

2. Then I update the Epic Name to "XXXX" and it disappears:

3. Then once more I update the Epic Name with some special characters "%$$ 123 ABCDEFG" and it reappears.

4. Finally I remove the special characters and it once more disappears!

WEIRD!

[Sarah Ware]

Hi, we are having a similar problem in Jira Cloud, where Epics in the same (classic) Project have the Epic Label as expected, but Epics from another (next-gen) Project we are not able to label - they display as "unlabelled-issuekey".

I have tried updating the label on the backlog view (below) but upon refresh the edited value is gone, and we are left again with "unlabelled-DT-1" for example. The issue type is included in the board filter as recommended in https://confluence.atlassian.com/jirakb/epic-tag-or-label-is-missing-on-sprint-board-779158640.html

[Angélica Luz]

Hi Sarah,

It looks like you're running into an existing bug, which can be found here:

- https://jira.atlassian.com/browse/JSWCLOUD-17761

Please be sure to watch it, so that you are notified when this is fixed in a future release.

Regards,
Angélica

[Barry Rudlin]

This is still an issue @Hayden Curry 

@Angélica Luz has there been any other updates on this issue?

[Angélica Luz]

Hi Barry,

I tried to replicate the issue again, but it's working normally.
Were the tickets imported as CSV the same as Hayden mentioned?
Please, give us more details about the steps you are following, so we can test here to check if it's a bug.

Regards,
Angélica

[Angélica Luz]

Hello Hayden,

Thank you for reaching out to Atlassian Community!
I've tested on my local environment but I wasn't able to replicate this issue.
Can you please let us know if this epic was created in this project or it was created on a classic project and moved to the next-gen one?
Is there any other next-gen project where the epic link is working correctly?
When did this issue start?
Please, let us know more details about the issue, so we can check here if this may be a bug or a configuration issue.

Regards,
Angélica

[Hayden Curry]

Hi Angelica,

Thanks for looking into this. In answer to your questions:

I imported the issues from a csv file directly into the next gen project.

Mine is the only next gen project on the instance.

This issue started as I began to populate the epics I imported with their child issues. Epics were imported and then I used the GUI to add stories.

One inkling I had was whether a duplicated epic name would cause a conflict bug?

Cheers,

Hayden

[Hayden Curry]

I've added some more examples

[Angélica Luz]

Hi Hayden,

Thank you for the details.
I tried to replicate this issue on my test environment, but after changing Epic name, it updates on the backlog normally for all stories.

We will need more details in order to replicate here:
What is the browser that you are using?
Can you open the developer tools while following these steps to check if some error appears when the epic disappears on the backlog? If so, please send us a screenshot of the error.
Would it be possible to test using another browser?
Are other users facing this issue?

Once we hear from you, we will follow the same steps to confirm if this is a bug.

Regards,
Angélica