Copy shared team from parent to created subtask with automation fails

Question

I'm trying to copy Shared Team information from parent to child with automation, but I can't make it to work fully.

I'm using automation "When issue created" with "Edit issue fields". With payload

{
  "fields": {
    "description": "{{issue.parent.team.id}}",
    "team": "{{issue.parent.team.id}}"
  }
}

I get the ID (4) to description of the child, but the Team dropdown is still showing "None". I've tried to use "customfields_10001" instead of "team", and the result is the same.

I've checked what https://xxx.atlassian.net/rest/api/2/issue/PG-32?expand=names says; for the parent the data is as expected, but the child has "null" for the value.

An interesting thing is that if I do a JQL "team=4", I get all the issues, but the details view is showing "None" for the team. If I export a list of these items, "Team Id" and "Team Name" are empty for the issues with team assigned with automation, but the original one has expected information there.

And the final thing is that if the field "Team" in the details view doesn't show any teams with the issues that has gone through the automation, but again with the original the field works. By "doesn't show anything" I mean that the dropdown does not show. Here's a pic where I have clicked a working and not working team selections:

Niklas Lampén · Answer

We only seem to have a single Team field at least based on the UI auto-completes and the information that the REST API endpoint returned about the issues.

The weirdest thing is that while the Team dropdown doesn't work, it's kind of set, as I can find the issues if I search with JQL "team=4". Still the API information about the fields says that the team is null for the subtasks, but the parent issue (team assigned manually) shows the expected object.

I'll contact support and post the findings here.

Bill Sheboy · Answer

Short answer: I recommend working with your site admin to submit a support ticket to Atlassian for this one, and to post back here what you learn: https://support.atlassian.com/contact/#/

Longer answer details...

Thanks for trying that test rule.  I am not using Advanced Roadmaps and so cannot test that one myself.

After I bit of research I found a few possible causes of this.  You may be able to try these to see how they help...

* With the beta of Jira Product Discovery, there are now two fields with the same name of Team, and this appears to cause some problems.  The suggestion on this this post is to rename the one of them...which I would worry leads to other side effects.  https://community.atlassian.com/t5/Automation-discussions/The-Team-field-s-and-Automation-when-using-Product-Discovery/td-p/1707420
* The field may not be editable if it is not present on the screens...although I would think that would throw an error in the audit log rather than silently fail.  https://community.atlassian.com/t5/Jira-questions/Advanced-Roadmaps-Teams-field/qaq-p/1847507
* I cannot currently find this one, and I recall a post that at least one of the "team" fields could not be written with the REST API available to customers.  If I find that post, I will update this one.

Niklas Lampén · Answer

Thanks for the answer, Bill!

The teams I'm trying to set are the Shared Teams found under Plan.

I did try with the hard-coded values as well, and the end result is the same. I was setting the team id for description as kind of debugging to be sure that whatever I'm doing is working at least for some part.