...

Requirement Yogi relies on "Application links" to communicate between Confluence and Jira.

• Jira has An applink exists with a given Applink ID (UUID) in UUID from Jira to Confluence,Confluence has another Applink ID (UUID) in Jira.
• An applink exists with another UUID from Confluence to Jira,

If you change the applink keys, all relations are broken. Your Jira issues won't be updated with the latest requirement text; the requirements won't list the related issues; and the list queue of messages between Confluence and Jira will fill up. To fix those, we've detailed the following steps.

...

Prerequisites

Those instructions are valid for Requirement Yogi 2.2.x and to 2.36.x.

You have first removed and recreated an Application Link between Confluence and Jira. Note: This wasn't the right thing to do for us, but you probably didn't know it, or didn't have the choice, so we'll help you from here. So, long story short: The new Applink exists and is connected, the old Applink was removed.

You've added a username for the new Applink in the Requirement Yogi administration in Confluence, tab "Integrations".

...

Get the old and new Applink ID

...

Depending on your database, the quotes can be:

• Not required,
• `
• '
• "
• [ ]

Code Block
language sql title Search for Requirement Yogi's integrations with other products
SELECT * FROM "AO_32F7CE_AOINTEGRATION" WHERE "SERVICEID" = "APPLINKID";

All the tables of Requirement Yogi in Confluence start with AO_32F7CE.

Note: Depending on your database, the quotes can be:

• No quotes,
• `table`
• 'table'
• "table"
• [table]

Here is the layout of the this table:

SERVICEID should be equal to APPLINKID for all links to Jira instances that were created using Atlassian's "Application links" system (the API is designed to support other types of integrations, but we haven't programmed it yet).

...