Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation Create New Issue On Another Project, Not Copying Custom Fields

John Lombardo January 25, 2024

I am trying to get an Automation to run the will clone a ticket to another project and move over data in some custom fields.

I looked at the documentation, that thought I had it setup properly.. But the field is still failing to show up on the clone

{
"update": {
"labels": [
{
"add": "cloned"
}
],
"issuelinks": [
{
"add": {
"type": {
"name": "Cloners"
},
"outwardIssue": {
"key": "{{issue.key}}"
}
}
}
]
}
{
"fields": {
"customfield_10207":"{{issue.customfield_10207}}"
}
}
}

 

This is the error I get:

Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Requesting on behalf (customfield_10207)

2 answers

1 vote
Walter Buggenhout
Community Champion
January 25, 2024

Hi @John Lombardo,

Requesting on behalf of is the reporter field. The text is a description that you can use in a service desk project when you create a ticket as an agent for somebody else. Whereas the reporter is usually filled out automatically with the user creating an issue, this is a case where selecting a different user overrides that system behaviour.

On a side note - I think you may also be making things more complex than they should be by using the advanced fields section. You can simply select the fields you want to fill out and specify to copy values from the trigger issue.

But for the specific error message, just copy the reporter field from your trigger issue.

Hope this helps! 

0 votes
Craig Nodwell
Community Champion
January 25, 2024

Hi @John Lombardo is that field available in both projects?  As suggested in the Error message please check the filed configuration and ensure it's available in both projects and the issue type.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events