- 
    
Bug
 - 
    Resolution: Duplicate
 - 
    
Medium
 - 
    None
 
- 
        29
 - 
        Severity 3 - Minor
 - 
        0
 - 
        
 
Issue Summary
If you wish to include issues from a Next-Gen in a Classic Scrum board filter the issues from the Next-Gen project which are part of an Epic in that Next-Gen project will not display in the backlog view.
Steps to Reproduce
- Create a Next-Gen project.
 - Create an Epic in the Next-Gen project.
 - Create some stories under this Epic.
 - Create a classic Scrum project.
 - Create a filter which picks up issues from both your Classic and Next-Gen projects.
 - Create custom board using this filter.
 
Expected Results
All issues appear in the backlog view of the classic board.
Actual Results
Issues part of the Epic in the Next-Gen project do not appear in the backlog view of your new classic board.
Notes
Issues that are part of an Epic in the Next-Gen project that a part of an active sprint will still appear in the respective columns in the main board view.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is duplicated by
 - 
                    
JRACLOUD-90578 Adding a team-managed (formerly next-gen) Project via Filters to the company-managed (formerly classic) Board shows the Epics of the team-managed (formerly next-gen) as unlabelled Issuekey
-         
 - Closed
 
 -         
 
- is related to
 - 
                    
JSWCLOUD-17902 Stories are disappearing from the backlog (in classic) when moved from a next-gen project
-         
 - Closed
 
 -         
 
- mentioned in
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...