We also need this fixed. We cannot use "roadmap" for a Service Desk Kanban because location doesn't match project issues.

This is just ridiculous. I can not add a kanban board to a project panel, and always have to force users to navigate through dosens of boards in the "Boards" section.

Think this should get improved.

BTW, when creating new board from existing project in latest Jira versions (7.+) "Location" field is missing. So i can not assign user defined boards to existing project/projects. Seems like this issues of the same flock.

not gonna get fixed if it doesn't "rank" high enough in the blah blah blah equation they use to determine priority... so keep waiting, it's only been 18 months.

We use JIRA Cloud across our organization, and it's disappointing that we have to convert our business projects to software projects as a workaround.

It's not appropriate for our non-technical users to be exposed to development tools unless we do the extra configuration to permissions to deny access to these features, same for agile boards that they won't need.

On top, JIRA does not allow Service Desks to be associated with Boards. Can't see any advantage in limiting associations of Boards. Plus I do have issues now with my Boards thanks to the latest JIRA Update.

I can understand no advantage to limiting board associations based on project type.  And applying this limitation creates complexity for customers who have existing boards built on business type projects.