How to manage tickets in two different projects

Question

We're currently using Jira v9.4.14.

We have one project (Project A) which is used by our PMO team.  They manage requirements, change requests and few other items in Project A.

We have another project (Project B)  which is used by our Development team.  They manage Epics, User Stories, Subtasks, Defects and Test Cases.

Both Project A and Project B are all related to one client project, just used my different groups and have different work flows.

This gets even more complicated as we have multiple client projects working in parallel and we have another project (Project C) for maintenance items for each client project.

Currently, the dev team is managing tasks for the CR in Project A plus other dev work in Project B, and thus managing two different projects and flows of work.

If a project manager creates a Change Request, CR, in Project A, how can the development team in Project B manage the tasks for the CR in Project B, without going into Project A and managing the CR directly?  IOW, team members in Project B want to work exclusively in Project B and not have to work/manage two projects.

Syed Majid Hassan -Exalate- · Answer

Hi @Scott Patrick

Welcome to the community! This is Majid @ Exalate.

Adding to Eugenio's answer, you can "sync" issues between different projects. So, for instance, Dev work in Project B and others teams want to send issues to Dev from their respective projects. They can Exalate tickets from within their own projects and the tickets arrive in Project B to be worked by Dev. Any updates that are made on either end and then synced across.

Hope it helps.

Thanks

Majid

eugenio_onofre · Answer

Hi @Scott Patrick

Welcome to the Atlassian Community!

Atlassian Automation can definitely assist with your problem. Please refer to the official documentation below.

In summary, the automations are structured in triggers, conditions and actions.

In your case, I would suggest creating an automation on Project A that does the following:

* Trigger: issue created
* Condition: if "issue type" is "Change Request"
* Action 1: create issue - here you will detail on which project you want the new ticket to be created + which fields you want to copy 
* Action 2: link issue to the newly created one

As for keeping both projects in Sync, you can definitely achieve it using Atlassian Automation, following the same steps I suggested above but changing the triggers, conditions and actions.

Please do not forget to accept this answer in case it helps you resolve your issue as it may help other community members in the future.

Regards,
Eugenio