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

[AS]

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.

[Matteo Vecchiato]

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

[AS]

@Matteo Vecchiato  thanks very much for your prompt response.

Can you please advise the steps to perform this task.

FYI- I tried the clone method. It worked but then I need to move the cloned item to the desired project. I am looking for some smart way to accomplish this job.

Thanks

[Steve S_]

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}}