How do I connect custom fields between multiple boards?

Question

Some background:

I am building out multiple boards again for a few different teams (one per team).

During the workflow for Team 1, an issue will be created. I want to have an automation which, when the issue is created, also creates a corresponding issue on Team 2's board to let them know to start working on their part of the assignment.

How I'm trying to map things now (which worked in the past but now gives me a vague warning that it can't be done) is where "Custom Field A" on issues from Board 1 get copied over into a matching "Custom Field A" in Team 2's board.

Question: Was there some kind of update which now forces this to be extra work to line up? Am I missing a step here? How can I get this to xfer over correctly?

The automation:

The issue type layout for Team 2

The issue type layout for Team 1

Here's the outcome/audit trail results as well

Ben Golder · Answer

Just following up:

Applying Smartvalues is hit or miss (sometimes I need to add ".value" and sometimes I don't and I have no idea what rhyme or reason exists here)

However, I haven't yet had time do to try out editing the JSON on anything.

Ben Golder · Answer

This is awesome and looks pretty familiar to how I've been plugging smart values in for things like the automated emailers that generate from the same board.

I'm really excited to try this out once the project automations page finally starts to load again lol.

I'll try this out as soon as I can and report back.

Andy Heinzer · Answer

Ok, so I had to play with this a bit to get it working, but yes, it is possible to get these values over to another issue using automation's smart values.  The problem here is that because these are project rules, the list of available fields is limited to fields in that original project.  So we can't directly select the destination field here.

However we can use the advanced fields to do this, we just need to make sure that we get the json payload correct when doing this.  In my own example, Project #1 has a custom field of text type called "ShortText1" while the destination project has a different custom field with the name of "shortertext".  In this example

{
"fields": { 
"shortertext": "{{issue.ShortText1}}"
}
}

When using this more options section of the automation action, there are additional fields that can be defined this way.

Try this, I got it working in my own Cloud site using automation. Both projects are next-gen in my testing.  Let me know if you run into any problems with this.

Andy