What is the best way to work with multiple teams

[Muhamad Laham]

We have 2 teams, developers and product.

currently, we are using the scrum board to manage our sprints and the product team put new tickets in the backlog so we can pull them when we start a new sprint.

But, we need to separate both teams, we want to create a board for the product only where they can work on creating their tickets and to have the ability to share/move these tickets to the developer once they finish it or when we start a new sprint.

[Nic Brough -Adaptavist- · Accepted solution]

I am not quite sure what you are looking for here.

It sounds like your product team are creating stories for your developers and your developers are working from a Scrum board to run their sprints.  That's exactly how I'd expect to work already!

I suspect you are saying that your Product people are doing something more complex than just creating stories for the developers.  Is there a process happening in the product team before the issues are created for the developers?

[Muhamad Laham]

@Nic Brough -Adaptavist- , this is how we are working right now, but I want to have a separate dashboard for the product team where they can create their own ticket before moving them to the dev team.

Actual: 1 scrum dashboard that the dev and the product teams are working on it

Expected: 2 dashboards, #1 scrum for the dev team and #2, Kanban dashboard for the product team. In the product dashboard, I want them to be able to move done tickets from this dashboard to the dev one in the next/relevant sprint.

In other words, I want a connection between both dashboards where I can move tickets from one to the other

[Nic Brough -Adaptavist-]

Ok, I'm a little confused because you've changed the words you are using and I don't know what the goal is now.

Are you looking at boards or dashboards?  (Or both).  I ask because although the underlying stuff is the same, the way to configure a dashboard is totally different to the way you configure a board.

There are a couple of underlying principles though - both rely on filters to define what they draw in to show you, and you should stop thinking of anything like "move" - dashboards and boards are not containers for issues, they display a selection.  No issue "moves" between boards or dashboards.

[Muhamad Laham]

It doesn't matter what should I use board or project or anything else. What I need is to be able to escalate the ticket that has already been done from the product team side to the dev team. I found a way like to add a custom field that contains 2 values, product, and dev, and add a filter for both boards to filter by this value. In this case, the tickets that have the value product will appear only in the board of the product and the tickets that have the value dev will appear only in the dev board

Do you have a better way to than this one? The problem in this way is that when I change the value of this field, the tickets will appear in the backlog but I want them to appear in the next sprint 

[Nic Brough -Adaptavist-]

That's not what you asked in your original question or follow-up.

How you would transfer responsibility for an issue from one team to another depends entirely on how you are representing that responsibility in Jira.  If it's the assignee, re-assign the issue, if it's a step in a process, move the issue through the workflow to the right step, if it's a field value, change the value of the field for the issue, and so-on.

We have been talking about boards and dashboards, I still don't know which one of those you are focussed on, so I can't talk about dependent visibility of issues.

However, on your last question, to add issues to a sprint, a human on the team who will be executing the sprint should be adding them to the sprint from the backlog, during sprint planning.  You shouldn't be just jamming things into a sprint because a different team thinks it's ready, and Jira simply doesn't support that broken process.

[Muhamad Laham]

Thanks @Nic Brough -Adaptavist- , got it