Issue solved by multiple teams

[Carlos Sousa]

Hi,

I'm deploying jira in my company and I'm doing this on a step by step approach.

First thing i did was to created Project A for a Team A to work. The project as an Email A account associated and everything is working great.

No I have Team B also wanting Jira to manage their work.

I can easily do the same thing, creating Project B handling the requests coming from Email B, but I want some more.

Some of the requests Team B  handles, need Team A  at some point and then return to team B for closure.

What's the proper way to implement this? Is there a way to take a ticket from Project B and "send" it to Project A. I know there's the "Move Project" option, but I don't think that's what I want.

Can you help?

Thanks.

[Jack Brickey]

you should not move between projects as it breaks the connection to the customer's request. What you can do is to open a ticket in Project B and link to Project A and you can use Automation to have the one in Project A 'follow' the one in Project B from a status perspective, i.e. have the one in Project A close when the one in A closes.

Alternatively, you manage via a single project and then use filters and Queues to manage the team's work. IMO this is generally the best option unless the frequency of passing an issue between teams is small.

[Carlos Sousa]

First of all thank you for your response.

I don't like the idea of shared projects. I image your are proposing to have 3 projects: A, B and AB for the shared tickets between teams A and B.

Now imagine I've have teams C and D. With this approach I'd need one project per team for single scoped issues (A, B, C and D) and one project for every single combination that I needed to segregate (AB, AC, AD, BC,, BD, CD, ABC, ACD, ...)

This is just impractical in the way I see it.

Any other option?