Can't see tasks from linked projects in Kanban Board

[Marie-Laure Cruyt]

I'm trying to do the following: 

Certain tasks from Project A (Next Gen) appear in the Backlog / Kanban of Project B (Classic) when they are in a specific status. 

To do so, I edited the filter query of the Board of Project B. I doubled checked, and when I run the filter, I see the tasks of Project A within the filter results. 
--> So my filter query is correct. 

I then checked the general settings of the Project Board B, and, in "Projects in this Board" both Project A and B appear. 

Finally, in the Columns, I mapped out the statuses of Project A in the Board columns of Project B, so this is not an "unmapped issue" problem. 

But when I get back to the Board, I still don't see the issues that I should from Project A.

I've already managed to do this before, and actually, in my Project B board I have issues from many different projects, so I don't get why the ones form project A aren't showing, even though I did exactly the same process...

[John Funk · Accepted solution]

Hi Marie-Laure,

So you run the filter attached to Board B and you see issues for both Project A and B as you desire? Correct?

But when you look at Board B, you do not see any issues from Project A - correct?

Have you checked for any sub-filters on Board B to make sure they are not further filtering issues?

[Marie-Laure Cruyt]

Yes exactly, when I run the filter attached to Board B, I see the issues of B and those I wanted to add from A. 


But when I get back to Board B, I don't see those issues. 

I did manage to solve it for one of my projects by removing the sub-filters. I had the following sub filters on Board B: fixVersion in unreleasedVersions() OR fixVersion is EMPTY
I removed them and I suddenly could see the issues from Board A. 

However, I'm doing the same exercise across several boards, always sending issues from Board A. I did exactly the same set up for Board C, also checking that the filter works, both projects are linked to the board and the issues are mapped. And I have the same issue.
But since Board C is a Scrum and not a Kanban, I don't see anything about sub-filters, so the same fix doesn't work :( 

[John Funk]

Just curious, but why would you have issues show up on a Scrum board that are not a part of the Sprint? That's probably the problem. Not sure that you will ever be able to solve that.  :-(

[Marie-Laure Cruyt]

Actually, I just want them to show in the backlog, and then assign them to the sprint. To give a bit more context, Board A is a board with all our marketing projects, and Board C is dedicated to our software tool. Sometimes, marketing projects imply having elements implemented in the software tool, so the idea was that the marketing team could somehow link those issues to the software tool board, so that they appear in the backlog and the product software team knows that these are also elements that need to be considered in the roadmap planning. 
But, I guess I'll figure something else. :) 

[John Funk]

Sounds like that should work, especially if it works with other projects. I still suspect it has something to do with the board somehow. Maybe it's the issue type being used on Board A? Is it different than the issue types on Board C?

[Marie-Laure Cruyt]

Yes, the issue type isn't the same because Board A is a next gen and Board C a classic Scrum project. The issues of Board A are main issues of a next gen project. 

[John Funk]

They can be different project types but still use the same issue types. I suspect the scrum board might not like the issue type you are using with Project A. You might try to move the issue type for the issue in project A to an issue type that is used in Project C - but keep it in Project A - just change the issue type (like Story or Task or whatever you use in Project C).

[Marie-Laure Cruyt]

In the end I switched Porject A from a next gen to a classic and that solved everything. Now all 3 projects are Classic Software projects and I could easily link them all. 

[John Funk]

That's interesting. Is there a difference in the issue types that you are using for the Classic project versus what you were using for the Next-gen project? We get this question a lot about adding Next-gen project issues to sprints so I am curious about what is different. 

[John Funk]

Any way, if you are good now, can you click on the Accept Answer button to close this one out?

[Marie-Laure Cruyt]

Sure! 
To answer your questions, both issue types were stories in both projects

[John Funk]

Okay - thanks!