How do I perform an automation task that lifts data points from one project to another

[Roy chege]

I'm trying to create an automation where when a transition happens across the Kanban board it lifts data from one project and creates an issue in another project. How do I automate a new ticket in a new project to bring data from a select list cascading field. With all other field types this seems to work, however with the Select List(Cascading) filed this doesn't seem to work

[Mark Segall]

Hi @Roy chege and welcome to the community!

Cascading fields have a little more nuance.  Can you please share a screenshot of your rule?  This will provide further context to help us help you out.

[Roy chege]

Hi @Mark Segall 

 The screenshot is attached, the issue is that cascading field doesn't appear under the 'choose fields to set' menu, when other custom fields do, hence looking for other options to transfer the data into the new issue for that field

[Mark Segall]

Yes - This is something that has to be set in the JSON.  You'll want something like this:

{ 
   "fields": {
      "FIELD-NAME" : { "value": "FIRST-LEVEL", "child": { "value" : "SECOND-LEVEL"} }
   }
}

[Roy chege]

Hi @Mark Segall thank you for this.

Further to specifying the field I'm looking to pull the value from the existing issue, into the new field once the transition takes place, this is still in reference to the 'choose fields to set' menu. Is this something that could be done within the JSON, allowing me to capture the data points and have them appear from Project A to Project B?

[Mark Segall]

Yes - You can use smart values in the JSON.  You'd just do something like this:

{{triggerIssue.YOURCUSTOMFIELD}} to populate the data.  So if you're doing a straightforward copy from project A to project B, it would be something like this:

{ 
   "fields": {
      "FIELD-NAME" : { "value": "{{triggerIssue.value}}", "child": { "value" : "{{triggerissue.child.value}}"} }
   }
}