One approach is to have them work in the same project. Then if you need to assign issues to one team or another you create a custom field with a team name drop down. You essentially virtualise the project for two teams.
The downsides:
- The project configuration is shared between the two teams so they need to follow the same workflows, issues types, screens...
- Maintaining the team assignment per issue is admin overhead
- The teams share the same sprint (unless you use paralle sprints - which has its own downsides) which means same start and end time and shared sprint reports. burndown charts etc.
The other approach is you put the issues and releases in a single project and the teams in different projects then those projects use a board that takes issues from the first project. I've never used this approach so not sure if it's feasible but it will be confusing (e.g. teams working in a project will accidentally search their own project for issues and won't find any).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.