Need your guidance in setting up a project

[Vikrant Yadav]

Hi Experts,

Need your guidance in setting up a project.

We have two teams A and B, B team pick the issues which are created by A Team and work on it.

Currently A is using separate project name A & workflow and B Team is having separate workflow & project B.

Now they are facing difficult to track all the things in a single issue. Because workflow is different, B team won't follow A Team workflow.

I suggested the following solution : Create an issue type in B project for A team and so that A team raise ticket directly in B projects and track there issue via issue type. With issue type easily filter out there issue and B Team also work on these issue without watching A project.

Second solution, i suggested to create an automation rule in A project which creates an issue in B project and link both the issue. In this case, A Team need to track both the issues A issue and B issue. Because team want to see progress of B issues as well. But in this ,, how user will find the linked issue for Project B. Project B issue are linked via Linked To link type with Project A. What would be JQL to get those issue ? Which are linked with Project A via Linked To link type.

Kindly suggest what would be collaborative approach and easy to user and easy to implement.

[Tomislav Tobijas · Accepted solution]

Hi @Vikrant Yadav ,

You might try using linkedissues() function but I don't think this will be efficient enough as, currently, you would need to specify issue key within the function itself.
For all advanced searching, I believe you would need to use some enhanced searches that are provided by some Marketplace apps.

Anyhow, I agree that the first solution you've mentioned would maybe be a better fit and less complicated.

With the second solution and linking, you could create some way of status mapping and comment copying - e.g. if A is transitioned to Status X, transition linked issue B to Status Y; and vice versa. Also, something like that could be created for comments as well. However, these automations could get a bit complicated at some point + in these scenarios, you're probably looking at a lot of automation executions on a daily/weekly/monthly basis.

Cheers,
Tom

[Vikrant Yadav]

Yes, in Linkedissue function we need to mention issue key. But we need to track issue without an issue key. 

[Tomislav Tobijas]

@Vikrant Yadav probably this won't be doable with native functionalities. The best thing I could come up with, when it comes to advanced searching, is using ScriptRunner's Enhanced Search. Specifically for this case, linkedIssuesOf() function.

[sai chinamuthevi]

First solution which you mention was easy to use.
Create an issue type in B for Project A and ask them to fill the required information. if you want after that you can link these as dependent by using automation rule