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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can I use components to run separate squads within the same project? Edited

Within our organisation we are looking to introduce Squads organised around Product level OKRs. In order to facilitate this, there is a requirement to set up and configure Jira projects and boards to support these new processes and team structures.

At present, work is divided across multiple Jira next-gen boards. Next gen boards have allowed our teams to ramp up quickly and start working independently however they are designed for a single team use case.

I would like to configure a Jira project so that each squad has its own view of the backlog, work in progress, and allow us to run sprints in parallel. Having read through the documentation and some of the community posts, it seems to me that one way of supporting this is:

  • Set up a new jira project
  • Configure each squad as a component
  • Create individual boards for each squad using the component as a filter

In the community's opinion would this allow for us to run the squads in parallel effectively? 

Each squad would have their own:

  • Stand ups
  • Sprints (and associated sprint ceremonies such as planning, review, and retro)

Does my jira configuration approach make sense?

2 answers

1 accepted

1 vote
Answer accepted

HI @Andrew Dunne 

You can use components to represent teams/squads and use separate boards for each within one project (backlog)... for Classic projects.  You cannot do this with NextGen as that feature is modeled around the simplicity of stand-alone, autonomous teams with one project-one board.

As you note, doing this for Classic projects is a good model of collaborating teams working on the same source backlog for a product.  Just define the boards and their filters to include ... AND Component = Squad1

As an added benefit, you can create a view-only, roll-up board for conversations like multi-squad touchbases (scrum of scrum in scaled agile).

Best regards,


Bill thanks for the answer, it's helpful validation for my approach that I've begun to experiment with but was still unsure whether I was on the right track. You've listed some valuable added benefits with regards to the roll-up board etc. I'll accept your answer.




Like Bill Sheboy likes this

I'd be interested in hearing others opinions on this topic as well!  I have multiple projects w/shared resouces using boards for team view, however w/covid impact measuring is difficult at best.

I'd love to hear more about how you generally configure a project for this use case @Tere Pile if you have an established way of doing it? 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,018 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you