Description:

There is a functional regression and parity gap between the Jira Legacy macro and the new Jira Work Items macro in Confluence Cloud when displaying issue counts.

When configuring the new Jira Work Items macro to display as a "Total work item count" (Inline), the macro successfully shows the numeric count for 0 issues or 2+ issues (for example: "0 issues" or "2 issues"). However, when the JQL query returns exactly 1 issue, the macro automatically overwrites the configuration and forces a single issue Smart Link text instead of the numeric count ("1 issue").

Steps to Reproduce:
1. Insert the Jira Work Items macro on a Confluence Cloud page.
2. Enter a JQL query that returns exactly 1 issue.
3. In the display options, select "Total work item count" (Inline).
4. Publish the page.

Expected Result:
The page displays a consistent numerical counter asset, showing "1 issue", keeping visual parity with the 0 or 2+ count layouts.

Actual Result:
The count layout is broken. The macro completely changes formats and renders as a text Smart Link to that specific single ticket (for example: "[PROJ-123] Summary of Ticket").

Business Impact:
This breaks the visual alignment, layout, and scanning reliability of automated status dashboards, tables, and KPIs. Users cannot build predictable report templates because a single ticket randomly alters the entire page layout.

This regression is a significant backward step from the functionality of the legacy Jira macro. I strongly hope to see this layout issue resolved before the legacy macro is fully deprecated by Atlassian, as otherwise many users and teams running automated dashboards will face this exact same challenge.