Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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

Christoph Dynowski May 16, 2024

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 set during clone, they may be unavailable for 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.

2 answers

2 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 16, 2024

Hi @Christoph Dynowski 

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

Christoph Dynowski May 17, 2024

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.pngBildschirmfoto 2024-05-17 um 10.11.19.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.

Bildschirmfoto 2024-05-17 um 10.18.13.png

 

----

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

Bildschirmfoto 2024-05-17 um 09.40.13.png

 

image (3).png

0 votes
Answer accepted
Christoph Dynowski May 17, 2024

@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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 17, 2024

Awesome; I am glad you got it working!

Like John Funk likes this

Suggest an answer

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

Atlassian Community Events