Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

With company-managed-projects, should the Jira project manage a team or a product?


This is a question regarding the way how we organise our teams and products. 

Current scenario:

We have multiple teams, and each one of those teams has multiple products (ranges from 1 to 20, depending on the team size). There's one Jira project per team, and each product is created as a "component". This eases the process (time-saving) and allows the use of Roadmaps, but it represents several difficulties when a product changes from one team to another, or a team is extinct and the product is inherited by another team. 

The documentation ends up getting scattered throughout multiple projects with different teams.



The proposal is for each product to have its own Jira Project. This way, all documentation (stories, tasks, bugs, defects, etc.) would stay in this sole project. Each team would need to use one Jira project that would have filters to catch and display the issues from those products assigned to that specific team.

That said, the projects for the products would be merely repositories, and the sprint workflow/schemes/columns/states would be a copy of the main management board.

Each team would have multiple boards but would manage issues on only 1 board, maintaining all needed metrics (sprint reports, velocity, etc.).



  • Does this proposal make sense?
  • How does the Atlassian team manage this?

(I also thought of a scenario where each product is a board inside one project, but would it be possible and easy to move one board + issues ownership from one project to another?)


P.S. - we have company-managed projects

1 answer

0 votes
John Funk Community Leader Aug 17, 2022

Hi Vasco,

Your proposal sounds good to me. I can't speak to what Atlassian uses or does though. 

One question do the Sprints span projects? Meaning that a single team might work on multiple projects inside the same sprint? 

Hi, John!

In this case, yes, a Sprint would have issues from more than 1 project. I'm thinking on teams that own more than 1 product, and there are sometimes requests from several products at the same time.

John Funk Community Leader Aug 26, 2022

Okay, that should be fine. You should be able to create a Scrum board that uses a filter that includes multiple projects. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events