Automation Rule: Copy data from single select list to text box.
Asked by Neeta Dubey:

Hi Team,

I creating ticket in JSM project and written a rule which created ticket in Jira project, however I want to copy data from select list "GCSD_Region" \[in JSM project\]to Region field\[In jira project\] and it shows below error. Please help if any solution is available.

Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -  
GCSSD_Region (customfield_20068)  
Issues created successfully.

![gcssd region.png](/t5/image/serverpage/image-id/340175i3F9209D7E09F0A9C/image-size/large?v=v2&px=999 "gcssd region.png")


Answers:
author: Walter Buggenhout
body: Hi [@Neeta Dubey](/t5/user/viewprofilepage/user-id/5287425),

If you want to set the value for a custom field while you create a ticket, that field should be on the *create issue screen* being used for the type of ticket you are creating in that specific project.

So check the project settings for your project, look for the screen being used for the create issue action for the issue type you are trying to create and make sure the GCSSD_Region custom field is on that screen.

Hope this helps!

comments: author: Neeta Dubey
body: Hi [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) :

Thanks for inputs, I'm copying rest all the fields and they are working as expected. The difference for this field is that, In the source project it is single select and trying to paste data in destination which is a text. I can manually create ticket in both the projects and both have fields presents.


author: Walter Buggenhout
body: I understand what you are saying, [@Neeta Dubey](/t5/user/viewprofilepage/user-id/5287425). However, the error message is not saying that your custom field is not of the correct type. It is clearly saying that you are trying to set an *unknown field*.

I now see though that you are using a *copy from current issue* action to set the value of the field in your target issue. You are referring to the GCSSD_Region field in both cases, which is not what you describe in your question. You said you wanted to copy the original field to another field in your target project. You should use the correct mapping between the fields there in your copy action.


author: Tomasz Kowalczyk
body: Ok, so what you're trying to do is to copy single select to text field. Have you tried to do it with smart values? like {{issue.GCSSD_Region.value}}


author: Walter Buggenhout
body: So you should be setting the Region field instead of GCSSD_Region.


author: Neeta Dubey
body: Hi [@Tomasz Kowalczyk](/t5/user/viewprofilepage/user-id/3784490) / [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) ,

I'm not getting option to set the smart value.![smart value.png](https://community.atlassian.com/t5/image/serverpage/image-id/340199iC221586DAE5F5075/image-size/large?v=v2&px=999 "smart value.png")


author: Walter Buggenhout
body: Hi [@Neeta Dubey](/t5/user/viewprofilepage/user-id/5287425),

You either copy the value from a field OR set a value where you can then enter a smart value.

If you hit the **...** button right next to where you now see *Copy GCSSD Region ...* you can either select *Copy*what you have done now) or SET, which will replace the current text with a text box. There you can then type in the smart value. As long as you are now setting the correct field (which I can't tell as the pop up is right in front of the field name there), copying as you do has a good chance of working as well.

You should get rid of what you pasted in the *Additional fields* box there. You don't need that and it will result in other errors like this.


author: Tomasz Kowalczyk
body: Do you have that field in destination project? First check configuration of that customfield. Maybe it's missing context but it look to me that field is not present on destination project.

comments: author: Neeta Dubey
body: Hi Tomasz,

Appericate your quick response. It is present at the destination, but it is a short text field. Is that causing the problem?


author: Tomasz Kowalczyk
body: Did you checked that field has context for destination and source project and just like [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) said it has field in issue create screen?


author: Neeta Dubey
body: Hi [@Tomasz Kowalczyk](/t5/user/viewprofilepage/user-id/3784490) / [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) :

Please see configuation of both the fields. Both are global fields.

![source.png](https://community.atlassian.com/t5/image/serverpage/image-id/340182i5FC4542CF830FCA2/image-size/large?v=v2&px=999 "source.png")![destination.png](https://community.atlassian.com/t5/image/serverpage/image-id/340183i82177010D7173C7B/image-size/large?v=v2&px=999 "destination.png")


Tags: automation-for-jira

cloud

jira-cloud