Jira Cloning: Link cloned issue to trigger issue

Alexandra Astor
Contributor
January 25, 2023

I have an automation rule that clones Issues from one Project (ITS) to another project (ATLAS) when a specific status is selected.  The problem is that the issues won't link together.  Both projects have permissions that allow a user to link requests manually between the projects.

Here is my automation rule in the trigger project:

Capture.PNG

When that didn't work, I also tried adding a rule to the destination project, but that didn't work either.   Here is that rule:

Capture.PNG

1 answer

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 25, 2023

Hello @Alexandra Astor 

The first version of your rule works for me.

Who is the Actor for the rule? Find that on the Rule Details page.

Alexandra Astor
Contributor
January 26, 2023

The Actor for the rule is Automation for Jira.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 26, 2023

Are the projects Software, Service, or Business projects?

In each project is the Link Issue permission allocated to "Project Role (atlassian-addons-project-access)"?

Alexandra Astor
Contributor
January 26, 2023

They are both service projects, and they both have the link issue permission allocated to Project Role (atlassian-addons-project-access)

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 26, 2023

This is a puzzler.

I created the same rule as your first one to clone an issue between two Service projects, including setting the link during the clone, and it worked.

Side note: you don't need to copy the Description or Assignee fields. Those are handled automatically by the Clone operation.

Are you using Issue Security in the destination project?

Alexandra Astor
Contributor
January 27, 2023

I am not sure, how can I check that?

Alexandra Astor
Contributor
January 27, 2023

This is what I am getting in the audit log.

Capture.PNG

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 27, 2023

To find out if Issue Security is applied you can look at the Project Settings, select the Summary page, and look for a section labeled Issue Security Scheme.

Looking at the error message I think, though, that the problem is the Linked Issues field is not on the Create Issue screen used for the Emailed Request type issue in the Atlassian Support project.

Go to the Atlassian Support project and click on 

Project Settings > Summary

Find the section labeled Screens. Click on the link for the Issue Type Screen Scheme associated . Example:

Screen Shot 2023-01-27 at 12.16.40 PM.png

 

Then click on the link for the screen associated with the Create Issue operation for the Emailed Request issue type.

Screen Shot 2023-01-27 at 12.17.41 PM.png

 

Look for Linked Issues in the list of fields. If it isn't present, you'll need to add it. You may also need to add it to the Edit Issue screen if that is a different screen than the Create Issue screen.

Screen Shot 2023-01-27 at 12.18.59 PM.png

Like Paula Garavagno likes this
Alexandra Astor
Contributor
January 27, 2023

AH ha that's it - thank you!

Like Karen Sanchez likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events