Workflows for each team - to distinguish the teams, you should set workflows for different teams. Best practice is to simplify these workflows by having less statuses.
Creating quick filters for each team - each team focuses on different things, so quick filters would save a lot of time for them
Create different boards for different teams and keep them simple - this means that your developers are not really interested in Forms section in the navigation bar, you can hide this - but you should tell your users about this because the board view is different for all users
You can create filters that will contain multiple projects in JQL query, so the visibility is spread across the teams with different projects. This could be one board only specific for that - do not go overbroad with the boards.
Use company managed projects - only they support having multiple boards (make sure you have a Jira admin for this)
Create unique dashboards for the teams - this depends on who needs to track the progress within the dashboards, make sure you include the filters that are covering multiple projects of your teams and use gadgets such as pie charts, workload chart, I assume your developers are using Scrum so you can use gadgets such as burndown charts. You can also use the two dimensional chart that can display multiple things at once such as issue type and the assignee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.