Just wanted to add my +1 for the previous feedback from @dromard. I’m a consultant that deploys and manages Jira for my clients, and both issues raised are significant problems for all of them (~15 Jira instance at this point).
In particular, the decision to attach boards to projects is a massive loss for my clients. These are services businesses that use the convention of 1 Jira project = 1 customer, and leverage “global” boards that are aligned to individual service delivery teams that each operate on Scrum or Kanban. Each team serves anywhere from 5-20 clients, and each team has a single board that aggregates the Epics and Stories from their respective customer projects. Before, it was very easy for team members to locate their board. Now, they have to dig around in their user profile, which is extremely unintuitive. As a workaround, I’ve been creating “meta projects” as a home for the board – these projects have no issues of their own, they simply aid in discoverability of the boards by Jira users. Better, but certainly not ideal. Does Atlassian not have engineering or support teams that work across multiple projects?
The other board-related problem I’ve faced is that it doesn’t seem possible anymore to copy an existing board (at least, it’s not available in the board actions menu, and there’s no longer a master board list). This is problematic because when we spin up a new team, we want the board (columns, card layout, issue detail view, etc.) to be identical to the other teams in the business. I used to be able to give my clients a template board to simply copy; now they have to create a new board and point and click through all the settings in one window while eyeballing the template board in another. Very tedious and error prone.
Anyway, I hope you find this feedback helpful. Happy to jump on a call to talk through my concerns in more detail if you’re interested, just DM me.