Page Comparison

...

Accessing the Requirement Yogi database in Confluence

Prefix: AO_32F7CE

All our tables are stored with the prefix “AO_32F7CE” (“AO_42D07A” in Jira, “AO_B895AB” for PSEA, it’s easy, it is the md5 of the plugin key).

...

• 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

• AO_42D05A_DBISSUELINK