Team field in JIRA Dashboard

[Vishal Biyani]

Now that Teams can be created centrally in JIRA, when will teams field become available in JIRA dashboard gadgets like two-dimensional filter statistics.

This is required as we are not getting the benefit of updating teams field at issue level.

Using a custom field to populate value in teams field is messy.

[Vishal Biyani · Accepted solution]

Anyone wanting to use JIRA automation can create an automation rule to update a custom field when Team field is updated.

The rule could be like:

---

When Team field is updated

Then Edit issue field and update below rule in "Additional fields"

{
"fields": {
"customfield_10111": {
"value": {{ customfield_10001.name.asJsonString }}
}
}
}

---

customfield_10111   Name of the custom filed to be updated

customfield_10001   Name of the Team field name in JIRA

[Dan Rico]

Why would we need to create a new field for a new field? I feel like this logic is backwards and counterintuitive.

[Matthew Wright]

Vishal posted and then accepted his own comment.  That is not accurate and so a moderator should remove the answer accepted.

We created a custom field populated with Team info long ago because of the visibility problem.

I posted to this: https://jira.atlassian.com/browse/JSWCLOUD-20787

last week because the new Team field should have wider visibility according to what I have read.  It is at least now assigned.  Not sure what that means.

For some reason, the Team field WAS visible in dashboard gadgets for a time as some of my users were actually using it in new dashboard filters.  I have no idea how long the field was visible.  Now it is unavailable and so they are not happy.

[Ricardo_Dinis]

Hello @Vishal Biyani

Instead of using  customfield_10001.name.asJsonString, use the id.

my example:

{
"fields": {
"Team": "12d30d16-10a5-4333-b9f6-da2040c01b3c"
}
}