Publishing search fields

Publishing writes 14 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.


#The fields

Field

What it holds

<hash>_capable_publish_status

Publishing state of the page. Declared by Suite, Publish and Approval apps. No the field list anywhere declares any publish field, so none of the fourteen appear in CQL autocomplete, they must be typed by hand.

<hash>_capable_publish_method

How the page was published (the publish method recorded on the source page).

<hash>_capable_publish_approved

Approvers on the publish record. Note the alias name says `approved` while the underlying JSON path is `approvers`.

<hash>_capable_publish_rejected

Users who rejected the publish.

<hash>_capable_publish_by

Account id of whoever performed the publish.

<hash>_capable_publish_when

When the page was published. Numeric timestamp, bare value.

<hash>_capable_publish_self

Whether this page is the publish 'source' or 'target'. Pages where this is `target` are deliberately skipped by real-time indexing, so their capable_refs data can lag.

<hash>_capable_publish_source_id

Content id of the source page a published page came from.

<hash>_capable_publish_target_id

Content id of the page this source page publishes to.

<hash>_capable_publish_parent_id

Content id of the parent under which the published page is placed.

<hash>_capable_publish_source_space_id

Numeric space id the publish originates from. Note this is a space ID, not the space KEY that Confluence's own `space` field takes.

<hash>_capable_publish_target_space_id

Numeric space id the publish goes to.

<hash>_capable_publish_missing_links

Links on the page that could not be resolved in the publish target, the field behind 'what would break if I published this'.

<hash>_capable_publish_can_publish

Whether the page currently passes its publish preconditions.



Indexed, then searchable. In that order.