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

Auto cloning issues from one project to another also autoclones 'Parent'

BenWade

Hi everyone,

I created an automation rule to auto-clone issues from projects A, B, and C into project BI and link them using the 'Clones' issue type link. Now, the problem is it also auto-clones the parent, which is a problem. What step should I add to the rule to stop it from auto-cloning the parent? The thing is, I have not added the 'Parent' field to copy from the current issue, but it still does.

#jiracloud

#jirapremoim

#companymanaged

Accepted answers

Bill Sheboy

Hi @BenWade

Would you please confirm what you are observing:

when an issue is cloned, the Parent field is also copied to the clone
when an issue is cloned, the entire Parent issue is also cloned

For the rule you show, the second one (clone the Parent issue) is not caused by that rule. Something else is causing the cloning.

For the first one (clone the Parent field), that field cannot be cleared by selecting it and leaving it empty in the rule action. Instead it may be cleared using advanced edit with JSON, by removing the Parent field from the dropdown selections and then expanding the "More options" section:

{
  "fields": {
    "parent": null
  }
}

Kind regards,
Bill

All comments

Matthias Gaiser _K15t_

Hi @BenWade

I'm not sure why this happens to you, but have some ideas how you could tackle the problem:

Is there another execution of your automation rule which copies the parent?
I assume your field "Clone to BI" contains some value like "yes" or "true" when it should clone to the other project, you could add an if condition which checks if this value is actually true.
If all your parents have the same issue type, maybe you want to add an if to your rule which checks for the type?

Maybe these thoughts help you in finding a solution.

Good luck,
Matthias.

BenWade

1) No

2) Correct. It auto clones when value 'true' added
3) Do not get it

I simply want the rule to not autoclone the parent regardless of the issue type.

Maybe I can manually add json here for the parent field so it stops autocloning it?

Matthias Gaiser _K15t_

My last point was more a follow-up to 1) if there was another execution for the parent in the audit log of your rule, you could define a condition to exclude your parent.

But I guess, I'm out of ideas for now, sorry 🫤

Bill Sheboy

Hi @BenWade

Would you please confirm what you are observing:

when an issue is cloned, the Parent field is also copied to the clone
when an issue is cloned, the entire Parent issue is also cloned

For the rule you show, the second one (clone the Parent issue) is not caused by that rule. Something else is causing the cloning.

{
  "fields": {
    "parent": null
  }
}

Kind regards,
Bill

BenWade

Thank you very much, @Bill Sheboy
I have just incorporated the provided json to mine and done 👍

{
  "fields": {
    "parent": null
  }
}

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

cloud

jira-cloud

premium

company-managed-projects