The "team" field is not visible on Dashboard Gadgets

[James Rickards (Spark-Nel)]

Currently we are looking to use "team" field to separate out which teams are working on issues in the one project.

However, the "Teams" field does not show up on Dashboard gadgets such as the two-dimensional filter gadget, or the issue statistics gadget.

This makes it harder to compare progress of issues in a project by Team.

Just looking to get feedback from Atlassian as to whether there is any plan to address this particular gap. I haven't spotted it on the roadmap.

[James Rickards (Spark-Nel)]

Related tickets here:
- https://jira.atlassian.com/browse/JSWCLOUD-20787
- https://jira.atlassian.com/browse/JSWCLOUD-26127

Example of a workaround here:
- https://community.atlassian.com/t5/Jira-questions/Team-field-in-JIRA-Dashboard/qaq-p/2516973

[April Chi]

Hey @James Rickards (Spark-Nel) ,

Apologies for the late response, saw this but didn't notice I didn't respond.

Thanks for the feedback 🙏 Acknowledging that this is frustrating and a feature that has been highly requested. I've noted this down in our backlog.

This isn't in the roadmap at the moment - our focus is on building Admin-Managed Teams and SCIM-sync Teams, which may take us to the end of FY25.

I'll share a quick internal roadmap later on our plans for FY25. 

Out of curiosity, do you primarily use gadgets for reporting? What do you look for in these reports? 

[James Rickards (Spark-Nel)]

Hi @April Chi ,

We use Dashboards for :

- providing a simpler experience for users who are new to Jira, and not ready to learn all the many different views, nor how to create their own custom filters to find the work they should be focused on.  For these users, I use the filter and two-dimensional filter gadget useful. Then I use the rich text gadget to add explanations with breadcrumbs such as "These are tickets needing Triage. Try to keep this list empty by updating the status after you review the ticket."

- a way of grouping several filters by a theme (e.g. daily work filters, or monthly reporting filters, or data hygiene issues).

- understanding workload spread across different projects, teams, or work areas where other OOTB tools are not more appropriate, or would place too much cognitive load on inexperienced users.

- supporting management or the team in understanding trends for meetings like a monthly retrospective. The Created Vs Resolved graph, two-dimensional filter is useful here, as well as the statistics gadget. Although I'd love to embed the Cumulative Flow graph from kanban boards into a dashboard.

[April Chi]

Nice! Thanks so much for the informative response @James Rickards (Spark-Nel) .

Once again, apologies, unfortunately this isn't a part of our roadmap for FY25 but this has been noted and your feedback will be used in our future prioritisation discussions. 

FY25Q2 is focussed on adding more controls to Teams and in case you're interested, we have SCIM-synced Teams coming up schedule for January release but you can join the EAP here: https://community.atlassian.com/t5/Atlassian-Teams-User-Group/Participate-in-the-SCIM-sync-Atlassian-Teams-Early-Access/ba-p/2821202.