Is it possible to edit the "Team" field through Jira automation?

[Connor Skiro]

In the image below, Jira recently added the "Team" field, however, it is not currently supported in Jira Automation. I tried looking for the smart value (thought it could be {{issue.Team}}), but Jira Automation did not seem to accept this JSON object.

[Bill Sheboy · Accepted solution]

Hi @Connor Skiro 

I do not know if the Team field is supported in automation, but you can try the steps in this how-to article to learn the supported smart values.  Basically you find an example issue and then call the REST API from a browser to list all the JSON contents.  Then look for your data to learn the name.

https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/

Once you learn if the field is supported, please post back the answer here.  Thanks!

Best regards,

Bill

[Connor Skiro]

Bill, 

You are an absolute genius! Following the link above, I was able to locate the "Team" field in the JSON object (see screenshots 1 and 2).

To validate that the field was supported, I created a rule to manually log the output when an issue was edited and received a successful response (see screenshot 3)

Lastly, as a quick proof of concept for the use case, I was able to update the "Team" field when the Component field was updated (see screenshot 4).

Thanks again for your help, Bill! I greatly appreciate it.

Best,

Connor

[Bill Sheboy]

Awesome!  I am glad you found the field and were able to update it.

Please consider marking this question as answered; that will help others with the same question find solutions faster.

Best regards,
Bill

[Tatianna Volamena]

Hi Bill, 

I am hoping you would be able to help me as well.

I am working with multiple Teams in the same Jira project.

I want the "Team" field to update when a task is assigned to a sprint. I was able to make the change for one team. But, I can't find the way to do it for other teams which are in the Jira Project.

Cheers, 

[Bill Sheboy]

Hi @Tatianna Volamena 

Please take a look at these examples for ideas how to do that:

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Multi-select-custom-field

What I do not know is what the attributes are of that field, such as "id", "value", etc.  You may need to first use this how-to article to learn the attributes to help pick the correct update syntax:

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill

[Tatianna Volamena]

Hi Bill,

Thanks for your feedback.

I did look into the links you shared. I played with my rules based upon the information provided. However, I was not able to find a way to get multiple teams / id in the same rule. :(

Cheers

[Bill Sheboy]

Hi, Tatianna. 

Sorry to hear that did not help.  What did you observe?  Did it the rule not save, show an error when running, not make the change when running, etc.?

Perhaps if you post what you tried in the advanced edit's JSON the community may notice something.

And also...unfortunately there are now multiple things called "Team" in Jira Cloud, and so using that how-to article to confirm your field actually has a smart value is important.  Some of the things called "Team" do not have smart values that can be changed by rules.

Kind regards,
Bill

[Tatianna Volamena]

Hi Bill, 

I tried both suggestion below. Problem is that the field doesn't get updated.

See below an example of what I tried.

[Bill Sheboy]

That appears to be a different field than you used originally: customfield_15300

Which one is correct, 15300 or 11600?  Whichever one it is, you probably should use "id" with the numeric id value for the team.

[Tatianna Volamena]

Hi Bill, 

Correct one is 11600.

Not sure that this is what you had in mind when you mentioned the use of "id". I tried with and without space with the numeric id value for the team but, it didn't do the trick. :(

[Bill Sheboy]

Pardon me if I was unclear; please try this to select the respective id values for the field:

{
  "fields": {
    "customfield_11600": [ { "id": 847 }, { "id": 853 } ] 
  }
}

[Tatianna Volamena]

Hello Bill, 

I actually tried this also but it doesn't work either. :(

Cheers

[Bill Sheboy]

Does it show an error in the audit log, not update the value, or update it with an unexpected value?

If it is none of those, I suggest working with your site admin to submit a ticket to Atlassian Support, as they may see something in the logs indicating what is happening: https://support.atlassian.com/contact/#/

[Tatianna Volamena]

I am not familiar with the audit log.

After I published my changes, I did some tests but nothing is happening.

I will reach out to my support team.

Thanks for your help.

[Tatianna Volamena]

Hi Bill, 

I worked with our internal support team and we found a way to make it work, see attached screenshot.

Here is an exemple of the :

- JQL condition sprint in openSprints() or Sprint in futureSprints() AND sprint = "xyz"

- update issue field

{
"fields": {
"customfield_11600": "xyz"
}
}

Cheers