...
However, the API of Confluence doesn’t allow us to perform proper aggregations. So, if you are a database administrator, you may want to understand how the data is stored, to be able to extract information yourself.
Please check out this tutorial for a quick overview: https://youtu.be/ruOAucnSxno?si=07gnqio1jHgeibZu&t=242
Disclaimer
| Warning |
|---|
Direct SQL access is not supported Accessing the database directly is neither supported nor covered by our agreement, since:
|
...
We’ll write more queries here, as customers ask.
Database schema
AO_32F7CE_DBREQUIREMENT
Primary key: SPACEKEY, KEY, BASELINE,
STATUS: ACTIVE, ARCHIVED, MOVED, DELETED,
HTMLEXCERPT, PROPERTIES
AO_32F7CE_DBDEPENDENCY
Primary key: RELATIONSHIP, PARENT_ID, CHILD_ID
AO_32F7CE_DBLINK
PARENT_ID: ID of the DBREQUIREMENT,
If ORIGIN=true, this is the page where the requirement was created,
If ORIGIN=false, this is a page that cites the requirement, or a Jira issue that cites it, since it depends on the type.
The primary key for this table is … almost all columns, since metadata varies per type of link.
AO_32F7CE_DBTRACEABILITYMATRIX
The list of saved traceability matrices,
Primary key: SPACEKEY, ORIGINALID
AO_32F7CE_DBQUEUE:
The queue (messages to Jira, indexation jobs or background jobs),
AO_32F7CE_DBBACKUPITEM and AO_32F7CE_DBBACKUPMAPPING:
Those are used as temporary storage tables when you export requirements to another instance of Confluence.
AO_32F7CE_DBAPPLINK:
Descriptor of Jira apps registered in Confluence, and opposite.
Accessing the Requirement Yogi database in Jira
Prefix: AO_42D05A
All our tables are stored with the prefix “AO_42D05A” in Jira.
...
AO_42D05A_DBREMOTEREQUIREMENT
...
Please go to Database schema for details about the SQL schema.