Versions Compared

Old Version 6

changes.mady.by.user Adrien Ragot

Saved on

compared with

New Version 7

changes.mady.by.user Adrien Ragot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

In Confluence

The Confluence part has now been replaced with a wizard, in 2.4.8. In the Requirement Yogi administration, click "Integrations", select the Jira instance that is disconnected, and there is a link "Fix applink" at the bottom.

Expand
titleClick here to expand if you use Requirement Yogi under 2.4.8...


We don't know what is the impact of performing these changes while Confluence is running, so by default we recommend shutting down Confluence. If you don't follow this recommendation, please at least disable Requirement Yogi temporarily before changing the database. (In development, we've always had success changing values in live, but in development we don't need reliability of data).

Code Block
languagesql
titleSearch 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 this table:

Image Modified

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).

Once you've determined what is the old and new "APPLINKID" (as per the table above), proceed to the next steps.

This table contains links and relationships between objects, and some of them are the Jira issues. 

Image Modified

In this table, only for records which have an APPLINK equal to the old applink and non-null, please update it to the new applink.

Code Block
languagesql
UPDATE "AO_32F7CE_AOREQUIREMENT_LINK" SET "APPLINK" = 'your-new-applinkid' WHERE "APPLINK" = 'your-old-applinkid';

You are going to move any message that was initially destined to the old Jira:

Code Block
languagesql
UPDATE "AO_32F7CE_AOINTEGRATION_QUEUE" SET "SERVICEID" = 'your-new-applinkid' WHERE "SERVICEID" = 'your-old-applinkid';

Here is the layout of the table:

Image Modified

If you have Requirement Yogi 2.3

If you have RY 2.3.x in Confluence, then you also need to update the table AO_32F7CE_AOISSUETEMPLATE.

Code Block
languagesql
UPDATE "AO_32F7CE_AOISSUETEMPLATE" SET "APPLINKID" = 'your-new-applinkid' WHERE "APPLINKID" = 'your-old-applinkid';


In Jira

Same as for Confluence: We recommend shutting down Jira and performing a backup before starting. If you don't, at least disable Requirement Yogi for Jira.

Yes, it is not the same as Jira's applink ID on the other side. However, this is much harder to determine. Please derive information by browsing the data returned by the following queryYou can easily determine the Appliink ID by going to the Jira administration → Application links → click on "Edit" next to the Confluence link → The ID is in the URL.

To confirm, you can run the following query and check whether the IDs match:

Code Block
languagesql
SELECT * FROM BANDANA WHERE BANDANAKEY LIKE 'applinks%';

...