nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Cloning: Link cloned issue to trigger issue

Alexandra Astor

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:

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:

Accepted answers

Trudy P Claspill

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.

All comments

Trudy P Claspill

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

The Actor for the rule is Automation for Jira.

Trudy P Claspill

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

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management