set customer request type when cloning issue using automation
Asked by Per Lofgren:

I have successfully cloned an issue using the action trigger in Jira Automation, and also linked the cloned issue from where it was created. This way I am able to preserve more field values than using the regular "create linked issue".

My issue now is that the request types are different and I need to set the request type. I want to set the new request type based on input variable using "Prompt for input when this rule is triggered".

I am having trouble finding the correct action to do this or can it be done even?


Answers:
author: Marc - Devoteam
body: Hi [@Per Lofgren](/t5/user/viewprofilepage/user-id/5388603)

Welcome to the community.

There is no option in automation for giving input when a rule is executing.

comments: author: Per Lofgren
body: Hi Marc,

Thanks for your answer.

There is an option to prompt for input and I have successfully manage to set the label for example on the cloned issue based on user input.

What I need to do is set the request type since the request type does not match in the other JSM project

<br />

![prompt.png](https://community.atlassian.com/t5/image/serverpage/image-id/298676iB3738413C8295BC7/image-size/large?v=v2&px=999 "prompt.png")  
![prompt2.png](https://community.atlassian.com/t5/image/serverpage/image-id/298680i2D0F55AC952D93D9/image-size/large?v=v2&px=999 "prompt2.png")


author: Marc - Devoteam
body: Hi [@Per Lofgren](/t5/user/viewprofilepage/user-id/5388603)

The only option I see, is to use a dropdown and set the options representing your request types and then set this to a custom field, as text or create a CF on the other project with the same options.

You can't use the Request Type field in the other project for this, as this is populated, based on the request types setup in that project.


author: Per Lofgren
body: Thanks for the reply Marc,

What I am trying to do is find a workaround for the limitation of adding fields to the create linked issue screen in JSM project since only required fields will show there. Hence my original question.

I don't see how a settings a custom field representing the request type value will help, unless a secondary automation changes the actual request type again.


author: Marc - Devoteam
body: Hi [@Per Lofgren](/t5/user/viewprofilepage/user-id/5388603)

There is no option to manipulate or have a workaround based on a trigger in automation.

The only next step you can take, in my opinion, is to raise a feature request at [Atlassian](https://jira.atlassian.com/secure/Dashboard.jspa). They might take this into account, but there is no guarantee that it will be implemneted.

Otherwise, Yes, you will have to use a secondary rule related to the CF filed option.


author: Per Lofgren
body: I believe this feature request from 2016 will help a lot of admins. <https://jira.atlassian.com/browse/JSDCLOUD-3917>   

Please vote for it if you have the same issue.  
Let's hope it does not rest for another four years.  
I don't like implementing advanced automation when it is a feature that should be built in already


Tags: automation

cloud

jira-service-management

jira-service-management-cloud