Cross project board not show all projects' issues

[Peter McManis]

There are a number of projects running in my org with resources spread across many. I want to be able to provide a Board that contains all live projects so that users can filter of themselves to see all work across projects.

I created a new "Oversight" board and linked in 5 projects using the SQL filter with accurate project codes. However some of the project issues do not appear. I suspected it might be whether they were company or team run but that did not seem to be the problem. 

Anu ideas why these project issues are not surfacing on my new board?

[Mohanraj Thangamuthu · Accepted solution]

Hello, Good day. As you have confirmed all 5 projects are present in the JQL filter query, we need to check the column mapping.

Go to column mapping in the board settings and make sure all status are mapped.

Other scenarios, could be that you don't have "browse project" permission on all 5 projects or issue security has been applied on the project.

[Peter McManis]

I had issues unmapped. Moving them from unmapped solved the problem. Thanks!

[Iván Pasarín]

Same problem here, but I have all the issues on all projects mapped and the browsing permissions to anyone in the org. The issues still won't show in the board... :/

[Trudy Claspill]

Hello @Iván Pasarín 

Rather then adding to old posts that already have accepted answers, please start a new Question by clicking on the Ask a question button at the top of the Community pages. Provide full details about your environment and your scenario, including screen images showing the configuration of your board and details about the issues that are missing.

Adding to old posts is considered necroposting, which is against the guidelines of the community.

Additionally adding to an existing post notifies only the post's original author, the people that responded, and people that are watching the post. So you request for help is not getting seen by the entire community.

And lastly, to give you assistance we need the details of your situation, which may be different than the post's original author.

[Iván Pasarín]

Thanks, Trudy!

I'm posting/replying to the post that appear in the search related to the issues I have. If I don't add further details is because the problem I experience fits the situation described in the original post, and I don't see the need of adding redundant information.

Anyway, already managed to solve the problem.

Cheers!

[Trudy Claspill]

You may want to review the Community Guidelines.

They speak specifically about necroposting, which would apply to your addition in this other thread.

Additionally, if you find a post that has an Accepted Answer, but the information in the answers does not solve your problem, then the best practice is to start a new Question. In your new Question provide a link to the post you found. Confirm which suggestions you tried from that post. Provide supporting evidence from your scenario to show configurations and examples of what you actually get vs. what you expect to get.

If the answer from the post doesn't work for you, then there is a good chance that there is something about your scenario that is different than the original scenario.

My recommendation is that new requests for help should always be posted as a new Question. As I said, when you add to an existing post there is a very small portion of the community that will see your addition.  If you start a new Question, then your request for help will show up in date-sorted list of Questions on the first page, making it more visible to the the majority of community members who go to that page to look for new Questions. With wider visibility your chances of getting help grow.

[Trudy Claspill]

Hello @Peter McManis 

Welcome to the Atlassian community.

Are the missing issues all of a specific type, from specific projects, or set to specific Statuses?

Did you create a Kanban board or a Scrum board?