Page Comparison

...

Important: Please set the administrator credentials

When

Status
colour Red title Important

 When requirements are changed on the Confluence side, we create messages in a queue that is sent to Jira. The queue used to be automatically sent using threads, but this is not regular enough and we've transformed the queue into a job. We need some credentials for this job, so that it can connect to Jira.

• Go to the Requirement Yogi administration,
• Tab "Integrations",
• Enter the username of a user who can modify any "Remote Issue Link" on the Jira issues that are linked to Confluence,
• Save.

Status
colour Red title Important

  For the moment, when the links of an issue in Jira are updated to reflect the changes in the requirement, the change is attributed to the credentials you've provided above.

What are those credentials for?

• Modifications in Jira will be performed under this username.If you also

• Status
  colour Yellow title In a near future

   Soon, if you upgrade the Jira side to RY 2.3, then Jira will display the real author of the changes in the history panel (as displayed in Confluence at the time of editing), instead of this username.

...

• No. It also fixes the bug where changes would be attributed to a wrong user. With this solutionAt least, in our situation, changes will are always be attributed to this the user in Jira, and that is specified ; and in a near future, Requirement Yogi in Jira uses another field to attribute changes to the correct original user.We'll only perform modifications to issue links ("RIL") will display the Confluence user who performed the changes.
• It is limited to only change the RIL ("Remote issue links") in Jira, and only those of type "Requirement Yogi" anyway.
• You're not giving "us" any information by providing your login here. If we just wanted some login, we could get it from the database. 

...