When cloning an issue, the new issue doesn't have a Request Type

[Tim Lee]

I have set an automation trigger to clone an issue when certain conditions are met. However, the clone does not inherit the "Request Type" from the original issue. So in my queue, that column is blank. Is it possible to inherit the Request Type when cloning an issue?

[Ana Livia Rocha Silva · Accepted solution]

Hi @Tim Lee 

Automation for Jira doesn't automatically copy the request type when clonning a ticket, however you can make that edit in another action in the same automaton. This article shows you how you can set the request type for the clone ticket.

From what you described, I believe you will need to create different if/else blocks for each request type on your project.

Hope I was able to help.

Kind regards,

Ana 

[Tim Lee]

This worked perfectly. Thank you!

[Luka Hummel - codefortynine]

Hi @Tim Lee

What you are seeing is expected: Jira Automation’s built-in “Clone issue” action leaves the Request Type blank. To keep the Request Type automatically, you can use Deep Clone for Jira instead of the default clone.

[SilkeS]

Hi @Luka Hummel - codefortynine , when you're part of an Atlassian Partner team, we kindly ask that you also include text in your comment stating you work for the company that built the app, per our Partner Rules of Engagement. Thanks!

[Joseph Chung Yin]

@Tim Lee -

In your automation rule, you will need to EDIT the issue again to populate the cloned issue.  Internally, the clone issue process is treated as issue creation not the same as issue creation via the portal UI where "Request Type" is invoked.

Hope this also helps.

Best, Joseph Chung Yin