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

Next-gen issues in an epic don't appear in classic project backlog

Dominic Sayers_a05atl

Bit confusing so I'll try to explain:

1. I have inherited a few next-gen projects with many issues; some in epics, some not.

2. I'm creating a scrum board that includes issues from several projects

3. The scrum board and its filter are in a new classic project I created just for this purpose

4. The filter shows all the issues I want in my backlog

5. The scrum board omits any issues from next-gen projects that have an epic but shows all the other issues.

6. Yes, I've properly mapped all the columns.

Is this a bug?

Here are the issues in my filter:

Screenshot 2019-09-04 at 10.37.59.png

Here is the backlog. As you can see it omits the issue from a next-gen project that has an epic but includes all the other issues:

Screenshot 2019-09-04 at 10.37.02.png

EDITED TO CLARIFY:

The only way I can combine issues from multiple projects into one scrum board is by putting the board and its filter in a classic project with a custom filter.

The filter is working fine, but the backlog based on it has missing issues as described above.

Accepted answers

Dominic Sayers_a05atl

Turns out this is a known bug: https://jira.atlassian.com/browse/JSWCLOUD-17987

All comments

Ollie Guan

Hi @Dominic Sayers ,

I think There are some differences between Epic for the next-gen project and the classic project, such as Epic Status, you can refer to the following post.

Missing Epic on board (next gen project)

Dominic Sayers_a05atl

Hi Ollie, thanks for taking the time to post an answer!

I think your answer refers to the board in a next-gen project. My issues are in a next-gen project but my board is in a classic project.

Nothing I do to the issue in a next-gen epic will make it appear in the classic backlog.

Dominic Sayers_a05atl

I've added a clarification in the question above.

Jack Brickey

Could you also provide the actual filter for your board here?

Dominic Sayers_a05atl

Hello Jack, thank you too for your interest and time!

Here is the filter that the board uses:

project in (TESTCLASS, TESTNEXTG) AND issuetype in (Bug, Story, Task) AND resolution = Unresolved ORDER BY created DESC, key ASC

Jack Brickey

thanks for sharing. something is amiss as that looks clean but let's debug a bit...

can you change your filter to simply

project in (TESTCLASS, TESTNEXTG)AND resolution = Unresolved

Dominic Sayers_a05atl

Good thinking. The filter now looks like this:

Screenshot 2019-09-04 at 13.33.57.png

and the backlog looks like this:

Screenshot 2019-09-04 at 13.35.35.png

So the epic is now there because we're not filtering it out. But its child issue TESTNEXTG-3 is still not there.

Dominic Sayers_a05atl

Turns out this is a known bug: https://jira.atlassian.com/browse/JSWCLOUD-17987

Jack Brickey

good work finding this. interesting that it is not listed as a sub-task of JSDCLOUD-8317

lua

Hi there,

Any update on this bug?

Markus_3ktnog

Same problem here...

Jack Brickey

Watch the reported issue via link above for any updates.

Emily Chan

Hi @Dominic Sayers , @lua , @Markus , and @Carol Wesolowski !

We're currently doing research on understanding more about organisations who are currently using both Classic and Next-gen project types at the same time. Would you help us learn more about you and your use cases?

A one-hour chat with you would be immensely helpful, and we’ll send you a $100 gift card as thanks. If you’re interested, please email me at echan@atlassian.com.

Dominic Sayers_a05atl

Hi Emily,

I don't have an hour to spare for this but in case you find it useful:

We have two classes of Jira user: (a) noobs who just want a simple to-do list and (b) experienced PMs who want full control
Usually the two sorts of project never have to interact so interoperability isn't a problem
Sometimes a simple noob project grows unexpectedly until it needs interop with a managed project.

That's when interop would be nice, otherwise we need to set up their project again from scratch, export & import, and change the way they work. Nobody likes any of that.

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