Description:

Background:
Following the automatic Jira Legacy macro → Jira Work Items macro conversion, the zero-results empty state behaviour changed in a way that is misleading to end users.

Previous behaviour (Jira Legacy macro):
When a valid JQL query returned zero issues, the macro rendered a clean table with column headers and an explicit "No issues found" message — clearly communicating that the query was valid but returned no matches.

Current behaviour (Jira Work Items macro):
The macro now displays:

"We couldn't find anything matching your search — Try again with a different term"

This implies the query itself is broken rather than simply returning zero results.

Steps to Reproduce:

1. Add a Jira Work Items macro to a Confluence Cloud page

1. Enter a valid JQL query that returns zero issues

1. Save and view the page

1. Observe the rendered empty state

Expected behaviour:
A clear, table-style empty state with an explicit message such as "No issues found" or "No issues match this query" — making it clear the query is valid.

Actual behaviour:
A large placeholder message that implies the query is invalid or incorrectly entered.

Business Impact:

• Customers using Confluence for release notes with multiple lines of business rely on zero-results being a normal, expected state

• Current wording causes end-user confusion — users interpret it as a query error rather than an empty result set

Proposed Solutions (either would resolve):

1. Restore the previous zero-count table format (showing 0 issues with the Jira filter link), or

1. Update the empty state message to clearly communicate "no matching issues exist" (e.g. "No issues match your query")