Versions Compared

Key

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

...

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.

...

Warning
titleBackup your database before proceeding

Please follow Atlassian's instructions about backups before proceeding. Although we, developers, change this data often, a non-experienced user may change the wrong data by mistake, and/or a heavily used application could have cached data at several levellevels.

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

...

...