Automation to cloned the ticket was not working if the issue type was "Same as issue type"

Tiodor Sianturi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 19, 2024

I have faced this issue when the setting was like this: issue type = "Same issue type" or "Same issue type as trigger"

jsm 1.png

with the errors:

jsm 2.png

but of the issue type = "Bug" or other issue type expect two of them it's working well. Can anyone help to find out why this happen?

2 answers

1 vote
Kalyan Sattaluri
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.
February 19, 2024

Hello @Tiodor Sianturi 

Welcome. I believe its a known issue. Please see below KB article. As you said, explicitly stating issue type should work.

https://confluence.atlassian.com/jirakb/automation-error-could-not-find-create-meta-data-for-project-typeid-1271695139.html

0 votes
Luka Hummel - codefortynine
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
February 20, 2024

Hi @Tiodor Sianturi and welcome to the community!

If @Kalyan Sattaluri is correct, you are trying to clone between a team-managed and a company-managed project. This isn't possible with the native Jira clone function. If you are willing to use a third party app you can use our app Deep Clone for Jira.

Deep Clone can clone between team-managed and company-managed projects. If you want to clone all issues created in a particular project you can also add a Deep Clone Post Function to the workflow of the project or use Jira Automation with a looping transition.

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