Jira issues search fields
Jira issues writes 2 fields into Confluence's own search index. Once a page has been indexed you can filter and sort by them in Capable Search, and use them in ordinary Confluence CQL.
A page Confluence has not indexed yet carries no values at all. It does not match a query on these fields, and it does not come back as an empty result either. On a large site indexing takes hours to days to catch up.
The <hash> prefix is your installation's app hash. Field names are written with it, so the exact string differs per site. Use the Copy CQL action in the search table rather than typing it.
#The fields
Field | What it holds |
|---|---|
<hash>_capable_refs_issues_count | NEVER FILLED. The field is offered in the list but nothing ever gives it a value. Always matches nothing. |
<hash>_capable_refs_issues_keys | NEVER FILLED, same as issues_count. Intended for Jira issue keys referenced on a page, but nothing fills it in. |
#Related
Indexed, then searchable. In that order.
