Problem With Linked Issue

[Razmik Mikayelyan]

EN: 

We have a Communication status in project A. When the task is transitioned to that status, it is cloning to Project B and coping linked issues from the parent task (from the task in project A). When the task transitioned to done in Project B, the task from Project A must clone to Project C. But here is the problem in Project C we need to copy the linked issues from project A, not from Project B.

RU:

У нас есть статус связи в проекте A. Когда задача переходит в этот статус, она клонируется в проект B и копирует связанные проблемы из родительской задачи (из задачи в проекте A). Когда задача перешла к выполнению в проекте B, задача из проекта A должна клонироваться в проект C. Но вот проблема в проекте C: нам нужно скопировать связанные задачи из проекта A, а не из проекта B

[Jimi Wikman]

Sounds like a chain of tasks, which is always better to keep in one place and not clone around.

Without knowing what you are actually trying to do, but looking at examples like E2E testing where you need people to do things in a chain it could be setup something like this:

1. Create a new Jira project for collaborative work.
2. Define the different parts of the chain and define labels or components (or even issue types) that will be used across multiple Jira projects.
3. Create a board for this Jira board so you can get an overview.
4. Update the boards for the other Jira projects (your projects A, B and C) to include the appropriate issues from the new Jira project.

This way you have one Jira project that focus on just these chains that can be used to oversee the chained work. The teams can continue working in their current Jira boards and just get more issues from this new JIRA project.