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

Automation Clone Issue - Description Fails "Unknown fields set during clone"

unknown

Unfortunately, I'm stuck with an automation for Jira Work Management.

The automation is supposed to be manually triggered and should clone the issue with all its children and sub-tasks.

So far, this works, and everything is cloned correctly. However, the description is not transferred, and I receive the following error:

Unknown fields <span>set</span> during <span>clone</span>, they may be unavailable <span>for</span> the project/type. Check your custom field configuration. Fields ignored - Description (description)

Here is the automation I have implemented:

https://community.atlassian.com/t5/Jira-articles/Clone-Epic-Stories-and-Subtasks-tree-with-Jira-Automation/ba-p/2316387

The funny thing is that it works in Jira Software and the description is also cloned. When the same automation is used in Jira Work Management, the description is not transferred.

I am grateful for any help and am also open to other automation methods.

In the end, a ticket should be cloned along with its tasks and the sub-tasks contained within.

Accepted answers

Bill Sheboy

Hi @[deleted]

For a question like this, please post images of:

each complete automation rules (with one image per rule),
images of any relevant actions / conditions / branches,
images of the audit log details showing the rule execution, and
explain what is not working as expected.

That solution approach requires multiple rules, so ensure you post all the rules and logs, identifying them accurately. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

That solution approach (with multiple rules adding / removing text from the summary) could have execution timing problems. Your rules could also be incorrectly accessing the Description field, as that error message seems to indicate multiple fields named Description. Please also check if that is the case.

Kind regards,
Bill

unknown

@Bill Sheboy

I really want to thank you.

After i searched for every field Configuration, i found out that the description was removed from the create Issue Screen.

That was the mistake.

All comments

Bill Sheboy

Hi @[deleted]

For a question like this, please post images of:

each complete automation rules (with one image per rule),
images of any relevant actions / conditions / branches,
images of the audit log details showing the rule execution, and
explain what is not working as expected.

That solution approach requires multiple rules, so ensure you post all the rules and logs, identifying them accurately. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

Kind regards,
Bill

unknown

Hi @Bill Sheboy and thanks for the quick reply.

As asked you will find the automation rules here.

Cloning Epic

To reduce the complexity of the Automation, i created a new one that should just clone an Epic with all prefilled Fields like Description, Assignee, Reporter from the Template KCC-145.

In Jira Software the Automation works perfectly, in Jira Work Management i get the issues with the Description.

Exptected Result:

- clone the Issue KCC-145 with all prefilled Fields.

Bug:

- The Descirption is Empty

Bildschirmfoto 2024-05-17 um 10.11.31.png

Also checked if it could access the Description field incorrectly. There is only one Field Called Description and its the default Field from Jira.

I can't find a difference between Jira Software Description and Jira Work Management Description.

----

The whole Automation with Childern & Sub Tasks just FYI.

Cloning the Epic and Childern (Tasks)

Exptected Result:

- clone the Issue KCC-145 with all prefilled Fields.

- clone the Children with all prefilled Fields

Bug:

- The Descirption is Empty

The Rule to Clone the Epic and Tasks:
Bildschirmfoto 2024-05-17 um 09.40.13.png

image (2).png

The Rule to Clone the Sub Tasks for each cloned Task:

Exptected Result:

- clone the Issue KCC-145 with all prefilled Fields.

- clone the Childern with all prefilled Fields

Bug:

- The Descirption is Empty

image (3).png

unknown

@Bill Sheboy

I really want to thank you.

After i searched for every field Configuration, i found out that the description was removed from the create Issue Screen.

That was the mistake.

Bill Sheboy

Awesome; I am glad you got it working!

Cyril Egan

@[deleted]

I had a similar error when trying to clone attachments. Your comment provided the solution to my error - Thanks you!

In my use case...

When the attachment field was not on the create issue screen and I had checked to clone attachments, the automation did raised an error in the automation audit log but did clone the attachments anyway.

When I added the attachments field to the create issue screen it cloned the issue with attachments without an error.

However I would think that the clone action should should clone attachments without error because there can be attachments on an issue that were not added on a create screen. I would think the same for your use case of "Description".

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

automation

jira-work-management

rule

jira-work-management-cloud