Clone an Issue and move it to another project

[Jinhui Kim]

When I cloned an issue and move it to another project, the cloned issue is connected to both projects. 

As you can see in the below picture, the issues in the blue circle are copied from OBCMK2 projects and moved to another project DCC2. But they are still connected to OBCMK2.

Is there any way I can disconnect these issues from the original project?

[Alexis Robert]

Hi @Jinhui Kim , 

I think there might be a misunderstanding on your side on what "connected to a project" means.

In this case, as you can see, the issue keys (DCCC2-85, etc) are referecing your DCCC2 project. 

The other issues on your screen are in the OBCMK2 project.

What you're seeing is the result of a JQL search, where you're looking for issues that match a specific field (requirementsPath). It means that your cloned issues, as expected, are perfect clones of the initial issues : they will have the same values for all the fields, including this "requirementsPath" field.

So to answer your question : you should clear the "requirementsPath" field in those issues if you don't want them to have that value.

It looks like this field is linked to the addon "R4J - Requirements Management for Jira" so maybe have a look at their documentation if you're unsure how to manage that field : https://easesolutions.atlassian.net/wiki/spaces/REQ4J/pages/5406729/User+Guide

Let me know if this helps, 

--Alexis