nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to assign a sprint to a team?

Hisham Balatiah

I have 3 teams working on my product, front end team, back end team, integrations team, and I need to start multiple sprints for all of them (I have enabled the parallel sprints), I have created multiple teams, multiple groups, multiple dashboard trying everything I can do to have this achieved, and yet nothing is working well with me.

I have created all my stories, epics, sprints and everything on a major dashboard, but I want to break them down to the hierarchy I mentioned above.

can anyone please assist in this case?

Comments

Curt Holley

Hi @Hisham Balatiah

Not certain I know what you are asking, but if each team has a board in Jira (ideally filtered by the Team field) and those boards have sprints, then this might be helpful? https://community.atlassian.com/t5/Jira-questions/Advanced-Roadmaps-capacity-planning-cross-projects/qaq-p/1574354#M461115

Dave

Hi @Hisham Balatiah ,

I would definitely second what @Curt Holley is proposing (and this is how we do it in for our teams). We also have multiple teams working from a single project and we create separate boards for each team. The basic steps to follow are:

Create your plan
Create your teams (commit and share them - sharing allows them to be queried using JQL)
Create JQL filters for each team - the filter should be all issues in the project assigned to specific team
Create a board for each team using the corresponding filter
Edit the issue sources of the plan and add the new boards
From the "Teams" tab, edit the teams and associate with the appropriate board

When you group by team you'll only see the sprints for each board from the team. You're going to want to make sure that you assign the appropriate issues to the appropriate team to get this to work properly.

The nice things about this approach is that each team can have their own backlog for the work they need to do in a project - and you can still retain a backlog of all work that is yet to be assigned to a team.

I completely appreciate that this is quite a convoluted process and we're going to be looking to simplify it and I'd love to get your feedback on the current process and how we could improve it.

To start with... do you think having a board per team is a good thing (as we're suggesting) or do you think parallel sprints in a single board is a better solution? If you like the idea of a board per team, would you want to be able to create and see that association on the board itself rather than just in a plan?

It would be great to get your thoughts on this!

Regards,
Dave

Hisham Balatiah

Hi @Dave ,

I would like to thank you for the explanation, I really do believe that a board for each team will match my needs more, as I deal with different resources, from different entities (outsourced) which they all serve and fall under one project, that's why I was interested at least to have different sprints to be run in parallel.

But I would also comment on the complexity of doing such setup, as I am new to JIRA, and I am reading as much as I can to do it, but yet I feel there something missing and I can't reach to it.

I will really appreciate it if you can assist in this complex setup, until we have a simpler way of doing it, or at least create project templates for (setup / clone) to match users needs and simulates the work environment each one of us has.