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

[Dominic Sayers]

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:

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:

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.

[Dominic Sayers · Accepted solution]

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]

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]

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.

[Jack Brickey]

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

[Dominic Sayers]

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]

Good thinking. The filter now looks like this:

and the backlog looks like this:

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]

Interestingly, the epic from the classic project (TESTCLASS-2) isn't there.

[Dominic Sayers]

If I show the epics pane in the board it looks like this:

But the unlabelled-TESTNEXTG-2 epic doesn't include any issues

[Jack Brickey]

well epics in NG are a different beast for sure. what i'm perplexed by is the fact that testnextg-3 isn't showing. and it is definitely the same issuetype, correct? 

So I just took a moment at did a quick test and indeed a child of a NG epic is not showing in the backlog. I fear the answer is that this is a known limitation.

I did a quick search of JAC but did not find any issue related to this. I may dig around a bit more to understand this. I may be missing something simple here but don't think so. You might get a quicker answer at Atlassian Support.

[Dominic Sayers]

> testnextg-3 isn't showing. and it is definitely the same issuetype

Correct.

Many thanks for your help, @Jack Brickey, I'll see if I can get any response from Atlassian.

[Carol Wesolowski]

Hi Dominic,

Did you receive any response from Atlassian?  I have the same issue with not seeing issues that are labeled with the same epic name between Next-Gen and Classic boards.

[Nicolas Chow Chin Sung]

I'm having the same issue. posting to follow the thread and any possible resolution. going to try an alternate implementation for now.

[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]

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]

I've added a clarification in the question above.