Issue Summary

Support the native Jira Team field (Atlassian Teams) as a selectable column/dimension in Confluence Jira Issues / Jira Work Items tables

Steps to Reproduce

1. In Jira Software Cloud, ensure the native Team field (Atlassian Teams) is available and used on issues:

1. • Go to a Jira project where Team is on the issue screen.

• • Confirm that issues have a Team value set and that the field works as expected in Jira and Plans.

1. In Confluence Cloud, edit or create a page and insert a Jira Issues / Jira Work Items macro:

• • Configure the macro with a JQL filter that returns issues which have the Team field populated.

• • Switch the macro to table / two‑dimensional mode (the view the customer uses for metrics).

1. In the macro configuration:

• • Open the Columns selector.

• • Search for or scroll through the list of available fields and try to add the Team field as a column / dimension.

1. Save the macro and the page.

Expected Results

• The native Jira Team field should be:

• • Available in the Columns list when configuring the Jira Issues / Jira Work Items macro.

• • Selectable as a column in table view, and as a dimension/axis in two‑dimensional reports.

• • Rendered using the human‑readable team name (e.g. “Payments Team”), consistent with how the field appears in Jira and Plans.

This would allow customers to use the same Team field as a single source of truth across Jira, Advanced Roadmaps/Plans, and Confluence reporting.

Actual Results

The native Team field does not appear in the list of available Columns / dimensions.

Workaround

Currently there is no native way in Confluence to use the Team field directly in Jira Issues / Jira Work Items tables.

A partial workaround is:

• Create and maintain a custom team field in Jira 

• Use Jira Automation to:

• • On issue creation and when Team changes,

• • Copy the Team name into this custom field (e.g. using a smart value such as {{issue.Team.name}} or the appropriate customfield_xxxxx name).

• Use this custom team field as a column/dimension in Confluence Jira tables.

This avoids manually updating two places, but it still requires a duplicate field and automation logic.

If you want to keep the FR description cleaner, you can summarize it like: