My two teams are thinking about merging into one but we need to still have a separation due to it being two different products being developed that rely on each other. what would be the best way to do this?
Hi Solomon - Welcome to the Atlassian Community!
Since these are two distinct teams, I would leave them in two distinct Jira projects. But then I would create a new board that uses a board filter which shows issues from both projects. This is all assuming that both projects are Company-managed projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi and welcome to the community!
Why do you want to merge the projects if it's still 2 different products with probably own releases, backlogs ...
The mergeing of 2 teams does not necessarily mean you need to merge the 2 projects which clearly represent 2 different products. Can you elaborate a bit on the "why" (why you think it is necessary to merge?)
Jeroen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jeroen,
Thank you for your quick response and welcome.
Project 1 was originally built a decade ago and has since undergone continuous updates. On the other hand, Project 2 is a new initiative categorized under the same directive as Project 1. Currently, we have 2 distinct teams working on these projects, and our goal is to merge them into a unified board where developers have the flexibility to select tasks from either project. Our release cycles are synchronized.
I was trying to decide if I should just make a new board on both projects that filters for both Project 1 and 2 so the active Product Owners create cards in their separate backlogs, or if there is a way to merge them but also have a way to distinguish which project an issue is addressing?
Best Regards,
Solomon
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.