Copying "Team" field from one JIRA project to another

Question

I still don't understand why Atlassian "locked" the "Team" field and made it so complicated to use,  but that's besides the point.

I am working on automation to create an issue in a project with the mandatory "Team" field, when some workflow transition happens in another project. The project field doesn't show on the list of the available fields in "Choose fields..." drop-down:

Is there another option (JSON?) to do so, similar to a cascading select list? I'd greatly appreciate community's help. Please let me know if you have any questions.

I've tried the below JSON option, but it doesn't work:

{
"update": {
"customfield_13600": [
{
"set": {
"value": "{{triggerIssue.fields.customfield_13600.value}}"
}
}
]
}
}

Gregory Kremer_mx3rfi · Answer

Trudy,

Thank you for your time and effort. There is nothing to be sorry about - some things just don't work the way we want them to.

Trudy P Claspill · Answer

Unfortunately I have not yet found any posts where a user was trying to copy the value of the Team field from a trigger issue to a related issue in Automation. And I don't have access to a Premium subscription to experiment with this more myself.

The only other option I can think of would be to use the Send Web Request action to access the JIRA REST API to try to get the original value and post it into the other issue.

Sorry I could not provide better assistance.

Gregory Kremer_mx3rfi · Answer

I've tried it without [ ] and with the "field" syntax as well as setting up a Log Action. The {{customfield_13600}} came back empty, while it brought corresponding value when I used it for another "regular" field. My guess is the "Team" field acts differently from other fields and I'd need to wait for Atlassian to fulfill a long promised change to this field. Unless someone could prove me wrong, which I'd gladly accept.