Cloned Issue: Edit Request Type Automation Not Working
Asked by Greg Costa:

I have two projects (Project A and B) that are both JSM. Project A used for HelpDesk and Project B used for Enterprise Apps. I created an Issue Type of Onboarding / Off-boarding that is associated to both projects. Both projects have an onboarding / offboarding request types (They are not the same but have the same fields added).  

I have an automation rule in Project A that clones an issue to Project B with specific custom fields to be cloned and linked back to trigger issue from Project A. This works fine.   

However, when the issue is cloned, the request type is left blank and the custom fields are shown in the context field and not under description field. If Project B request type Onboarding / off-boarding gets added, the fields are in the right place.  

To ensure the issue has the request type added automatically, I've created an automation rule in Project B to 'Edit the request type' but this doesn't work. The audit logs reviews all issues except for the cloned issues.


Answers:
author: Trudy Claspill
body: I'm afraid I've run out of ideas and not finding other suggestions through internet searching.

At this point I recommend you open a support case directly with Atlassian for additional help.

<https://support.atlassian.com/contact/#/>

And it would be great if you can report back here what the solutions turns out to be.

comments: author: Greg Costa
body: Thanks [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) . Strangely enough, I was able to resolve this issue by configuring Project A automation rule with 'Create a new issue' instead of 'Clone issue.' When corrected, Project B automation rule kicked in and edited the request type perfectly fine. ![Screenshot 2024-07-08 at 12.07.46?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/334086iE1493338C561571A/image-size/large?v=v2&px=999 "Screenshot 2024-07-08 at 12.07.46?PM.png")


author: Trudy Claspill
body: Hello [@Greg Costa](/t5/user/viewprofilepage/user-id/5470139)

The step to Clone Issue does not thereafter change the focus of the rule to the newly created issue. When your rule reaches the Edit Request Type action, it is executing that action against the issue that triggered the rule, not the issue created by the Clone action.

In order to modify the issue created through the Clone action you will need to use a For Each branch.

For Each / branch rule/related Issues / Most Recently Created Issue

![Screenshot 2024-07-03 at 2.09.22?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/333401iBA8FCA3561CD2458/image-size/large?v=v2&px=999 "Screenshot 2024-07-03 at 2.09.22?PM.png")

In order for this to work, on the Rule Details page this rule must be set up as a Multiple Project rule and name both the source project and the destination project.

In that case you may want to add another condition after the trigger to check the Project of the trigger issue to ensure that it was an issue created in your intended source project. Otherwise the rule will be run for new issues created in the destination project also.

comments: author: Greg Costa
body: Hi [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) , thank you for the information. The suggestion you provided is not what I have in place. The clone automation rule occurs within Project A but 'Edit Request Type' automation occurs within Project B.


author: Trudy Claspill
body: Thank you for the clarification.

Check the Rule Details page of the rule in project B. Confirm this checkbox is **checked**

![Screenshot 2024-07-05 at 8.39.50?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/333750iC99B689A5A35785E/image-size/large?v=v2&px=999 "Screenshot 2024-07-05 at 8.39.50?AM.png")


author: Greg Costa
body: The error I receive now is the following:  

![Screenshot 2024-07-05 at 12.47.57?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/333764i49DED5262DD98B91/image-size/large?v=v2&px=999 "Screenshot 2024-07-05 at 12.47.57?PM.png")  

That custom field is the Request Type Field. What is required to resolve this issue?


author: Trudy Claspill
body: If you view issue EA-6319 through the UI, do you see the Request Type field and can it be edited?

Who is the Actor for the rule?

Is the EA project Company Managed or Team Managed?


author: Greg Costa
body: I can edit the request type manually in Project B and that would resolve the issue of seeing my fields under context instead of the correct location under description. The actor is me. The Project is service managed. That was written in my original request (JSM - Jira Service Management)![Screenshot 2024-07-05 at 1.12.00?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/333770iE123C4DC8657ED00/image-size/large?v=v2&px=999 "Screenshot 2024-07-05 at 1.12.00?PM.png")


author: Trudy Claspill
body: Is the EA project Company Managed or Team Managed?


author: Trudy Claspill
body: For issue EA-6319 can you use the guidance in the following document to get the output of all fields associated with that issue and confirm that the ID for the Request Type field is 10010?

<https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/>


author: Greg Costa
body: They are both company managed projects


author: Greg Costa
body: ![Screenshot 2024-07-05 at 1.21.21?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/333773iDD2432394A3A4584/image-size/large?v=v2&px=999 "Screenshot 2024-07-05 at 1.21.21?PM.png")


author: Trudy Claspill
body: Can you check one more thing, please?

Go to the Settings (gear icon near your avatar) / Issues / Custom Fields screen and lookup the Request Type field. Then click on the ... button next to it on the right and hover over one of the options that comes up. Then look at the URL that appears at the bottom of the browser to check the field ID number that displays there.

![Screenshot 2024-07-05 at 1.26.04?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/333794i1C42442BFEF8E4D8/image-size/large?v=v2&px=999 "Screenshot 2024-07-05 at 1.26.04?PM.png")

That message typically means that either the field is not on the Edit screen, or the actor doesn't have permission to change the field, or the wrong field is being referenced. You have told us you are the actor and you can edit the field directly, so the field would seem to be on the Edit screen and editable by the rule actor. The action should be referencing the system-provided Request Type field by default, and the ID you got for the field matches what I get in my own system.

I just found this KB that talks about this error coming up if there are two Request Type fields. Is that the case in your instance?

<https://confluence.atlassian.com/jirakb/unable-to-update-request-type-using-automation-rule-getting-error-field-customfield_xxxxx-cannot-be-set-it-is-not-on-the-appropriate-screen-or-unknown-customfield_xxxxx-1295390355.html>


author: Greg Costa
body: Yes, the custom field ID is the same. No, I only have 1 request type field.

![Screenshot 2024-07-08 at 8.19.06?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/333996iCF32D46784799881/image-size/large?v=v2&px=999 "Screenshot 2024-07-08 at 8.19.06?AM.png")


author: Greg Costa
body: ![Screenshot 2024-07-03 at 1.07.31?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/333362i902F8F8CBE9680A4/image-size/large?v=v2&px=999 "Screenshot 2024-07-03 at 1.07.31?PM.png")


Tags: cloud

jira-service-management

jira-service-management-cloud