How can I mirror an issue or epic on different projects?

[Workaround12]

Hello,

I would like to know if it is possible to mirror the same issue or epic on different projects? For example we would like to have one project for the developers (workers) and one project for the management. On both boards we would like to have the same epic or issue for main information and linking subissues etc.. but we only would like to create subtasks or create connected issues on the developer board. So the manager board doesn´t get overwhelmed with subtasks.

Do you have any ideas on this? Experiences?

[Riddhi Shah]

Hello @Workaround12 ,

As @Matthias Gaiser _K15t_ rightly said that you have a classical use case of an issue synchronization.

I'm Riddhi from team Exalate, which is a live sync tool.

Exalate is made for your use case as it allows syncing information bi- and uni-directionally between multiple Jira instances. Or separate projects in your local Jira.

It's mega flexible, you can sync all types of information, including comments, attachments and custom fields. You can control what to sync and what not, and much more ....

It can also cater to your situation of dealing in a private to public sync, You can find out more about it here.

By the way, It might also be useful to set up a live video-discussion to demonstrate how Exalate would get set up for your use case

Would that be valuable to you? You can book a suitable slot here.

Cheers,

Riddhi

[Matthias Gaiser _K15t_]

Hi @Workaround12,

I can see some possible solutions here:

• You could work the usual way in your development projects and create another board for your management. In the management board you would configure the filter to exclude subtasks (or other issues you want to hide).
• You could use an issue synchronization app. I'd then recommend you to create a project for your management and setup synchronizations between the development projects and your management board.
  Depending on your choice, it might be enough to synchronize unidirectional to the management project, but you could also choose to synchronize some information back.
  I'm working for the team behind Backbone Issue Sync, so I can say our tool fulfills the requirements you stated - but also the others are fulfilling these requirements.
• You could also have a look at Jira Portfolio (depends on how big you want to go here).

Maybe someone else has other thoughts to contribute?

Cheers,
Matthias.

[Steve Kim]

Hi,

In your 1st option would that also prevent the sub-tasks from showing up on the active sprint page?  Assuming this isn't a Kanban board sub-tasks usually don't show on the backlog screen.

Thanks,
Steve