Opening Jira Bug in two projects simultaneously by logging in either project.

Question

I have customer services and customer complaints projects as two separate spaces in JIRA.

I want to know if there is a way to link these two spaces/projects in such a way that if Bug is opened in one space, then I should be asked to choose if this bug needs to open in another space.

Not sure if this is possible but, if it is then it can save a task to open same bug in another space.

Olga Cheban _TitanApps_ · Answer

Hi @AS !

It looks like for your use case, a viable solution would be to set up automation that is triggered manually. This means you set up a Jira automation rule / flow, but select Manual as the automation trigger, but select manual as the automation trigger.

Here's an example of what a rule can look like:

Then you can open your bug and trigger this automation from the Actions (Lightning Bolt) menu, like in the screenshot below. This menu will show the list of automation rules to choose from after you set them up (if you don't have any yet, it will be empty).

So the bug or another ticket is cloned to the different project specified in the automation rule when you decide it's necessary. You will not have to transfer it to another project manually. You will not have to transfer it to another project manually.

I covered this flow in more detail, along with other cloning options, in my article The Complete Guide to Cloning in JIRA in 2026, so it might be a useful read.

I hope this helps!

Clara Belin-Brosseau_Elevatic · Answer

Hi @AS

If you want an easier alternative to do this, our app Elements Copy & Sync can handle this kind of cross-project workflow. The app allows to automatically clone Jira issues from one project to another and keep them synchronized if needed.

These would be the set up steps:

* You create a "Copy and Synchronize work items" recipe from your Customer Complaints project to your Customer Services project (or vice versa).
* You can set the recipe to trigger automatically on issue creation (or on a specific status/transition, e.g. "when Bug is created" or "when moved to Confirmed"), so the moment a Bug is logged, a linked copy is created in the other project — no manual duplication needed.
* The two issues stay linked, and you can choose which fields (status, comments, attachments, etc.) stay synchronized both ways going forward, so updates in one reflect in the other.

This avoids the "open it twice manually" step entirely, and also solves the follow-up problem of keeping both issues aligned as the bug progresses.

If you'd rather keep it a manual/optional trigger (choose whether to open it in the other project each time, as you described), that's also possible, you'd just run the recipe manually from the issue instead of automating it.

Happy to point you to more detail if useful.

Javier Pozuelo -Exalate- · Answer

Hi @AS I’m a Solution Engineer at Exalate.

Steve and Matteo already covered the main native options well. If the goal is only to make the same Bug visible to both teams, Steve’s suggestion of using a shared board/filter may avoid creating a duplicate altogether.

If you do need two separate Bugs, then Jira Automation is probably the simplest approach. A Yes/No custom field can trigger a rule that creates the second Bug directly in the target project, maps the required fields, and optionally links both issues. This also avoids the clone + move step you mentioned.

One additional consideration is what should happen after the second Bug is created. If the two issues are independent, Automation should be enough. If changes made afterward also need to stay synchronized between both Bugs fields, statuses, comments, attachments, etc. then a local synchronization solution such as Exalate could be useful for keeping the two issues aligned.

Good luck with this use case!