Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Create a Project Administrated by Company or by Team

I´m starting a project administrated by company. In my team we have 4 squads and we need starting multiples sprints.

Do I need to create a specific project for each squad or one project for all? What would be best since I need multiple sprints?


It´s better create a individual projets but administraded by team?

1 comment

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 20, 2022

Sprints are associated with Boards, not Projects. Boards are a way to view and manipulate issues that are in projects.

There is an option to globally enable Parallel Sprints which will allow you to have multiple Active sprints in a board.

Alternately, for a Company Managed project, you can have one project and create a separate board for each team. The boards in that scenario would be based on Saved Filters where you have something in each issue that indicates to which Team the issue should be displayed.

Are your teams working on the same releases or different releases? If your teams are working together to produce a shared release, then I would recommend one project. If your teams are working on code that is releases independently from the work of other teams, then I would recommend separate projects.

If you want to share work between the teams I would recommend Company Managed projects. Team Managed projects are intended to be stand-alone. You can't share issues or configurations between Team Managed projects.


Log in or Sign up to comment