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

Hi @AS 

Thank you for your post.

For implementing this you should:

• Create a custom field and put it inside the the create screen that ask for creation in another project (yes/no)
• Create an automation that, based on the field and original project, create a clone in another specific project

Hope it helps

Hello @AS ,

First, ask yourself why you need to clone the ticket?  Your other project should allow for a dedicated board (project board or a shared dashboard).  This way, you can simply filter on the incident being created in one project, and still have it show in that other project's board or a shared dashboard.  

To answer your question directly as asked:

Instead of cloning, you may want to create the copy of the ticket via an automation rule.  This way you can determine exactly what fields to create and which project to place it in.

Steps
1. Navigate to Automation

Go to Project Settings (source project) → Automation → Create rule

(Or use Global Automation if this rule should apply across multiple projects)

2. Set the Trigger

Select Issue Created as the trigger

(Alternatively, use Field value changed if the "Yes" response can be updated after creation)

3. Add a Condition

Click + Add component → Condition

Choose Field condition

Set: [Your trigger field] equals Yes

4. Add the Action

Click + Add component → Action

Choose Create issue

Configure the following:

Project: Select the target project

Issue Type: Match the source type (e.g., Bug)

Summary: Use a smart value like {{issue.summary}} to carry over the title

Additional fields: Map any other fields you want copied over (description, priority, etc.) using smart values such as {{issue.description}}, {{issue.priority.name}}

5. (Optional) Link the Issues

After the Create Issue action, add another action: Edit issue

Use Link issues to create a relationship (e.g., "clones" or "relates to") between the original and the newly created ticket

Reference the new issue using the smart value {{createdIssue.key}}

6. Name and Enable the Rule

Give the rule a descriptive name (e.g., "Cross-Project Ticket Duplication on [Field Name] = Yes")

Set the rule scope/actor (the user account the automation runs as)

Enable the rule

Key Smart Values to Know - I advise you to look them up 
{{issue.summary}}

{{issue.description}}

{{issue.priority.name}}

{{issue.reporter.accountId}}

{{createdIssue.key}}

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!

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.

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!