how to link issues after creating a new issue and assigning it to a new project via create/clone act

Owen Dubiel

Hello, here is the scenario: Our vulnerability scanning tools are set up to create tickets in Jira. I need to create an automation that for every new ticket created within our VULN project, it assigns the ticket to another Project within our instance. The only way I found to do this is to use the clone or create new ticket action. Which is fine, if I am able to link the newly created issue with the one created from our vuln scanning tool. I keep getting stuck at the link issues options. could it have something to do with cross project permissions? I am able to manually link.

Bill Sheboy

Hi @Owen Dubiel  -- Welcome to the Atlassian community!

Returning to your original problem, once the issue is created in the VULN project you could simulate a move to the other project by clone and delete (or close).  Then you can avoid the linking issue.  Please see this documentation for a how-to:

https://support.atlassian.com/jira-software-cloud/docs/move-an-issue-with-automation/

To confirm this works correctly..

• You may want to re-fetch the issue after the trigger, and before the clone
• Rather than delete, you may want to close the triggering issue.  Once things are deleted they are gone, so it will be difficult to diagnose problems otherwise.

 

Best regards,

Bill