Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Confluence
/
Release 2.2 – Change the queue implementation with Jira
Updated Jan 04

    Release 2.2 – Change the queue implementation with Jira

    This release contains changes which are necessary for the performance in cluster environments and for the Data Center certification. Among those, administrators must add some credentials in the Requirement Yogi administration for the integration with Jira. There is no "actual feature" in this release.

    ❗️ Please set the administrator credentials

    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.

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

    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. As a reminder, this was necessary because messages from Confluence are processed in batch and allows us to gain performance.

    What are those credentials for?

    • AUTHOR IS LOST: Modifications in Jira will be performed under this username, not under the name of the person who performed the change.

    • IN A NEAR FUTURE: Next month, if you upgrade the Jira side to a version 2.2.x that we'll publish for Jira, 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.

    Should I be worried that my login is being used here?

    • No. It also fixes a bug where changes would sometimes be attributed to a wrong user anyway. At least, in our situation, changes are consistently attributed to one administrative user; and in a near future, Requirement Yogi in Jira 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".

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

    What happens if I don't provide a login?

    • The message queue fills up, the table AO_32F7CE_AOINTEGRATION_QUEUE will become large, and there will be messages in the Confluence logs.

    Other changes

    • We've managed the queue (of messages to Jira) as a scheduled job. You can now configure how often this queue executes, you can disable it or run it on demand.

    • We've changed the caches for the Dictionary blueprint, for the baselines, for some background tasks and their error reporting, so that all of those caches are properly shared on a cluster. We've also measured their performance in preparation for the Data Center certification.

     

    Changes in the RY for Jira module

    • It is better to also upgrade the Jira module. Using this module, changes will correctly be attributed to the original author. If you remain below version 2.2 in Jira, changes will be attributed to the user provided in the form above.

    • We've summarized everything about the Jira migration on this page.

    • RY-107 We've fixed the "bodyfields" box.

    List of Jira issues

    See the list of Jira issues here.

    type key summary assignee reporter priority status resolution created updated due
    Loading...
    Refresh





     

    Teams
    , (opens new window)

    Requirement Yogi (Data Center)
    Results will update as you type.
    • Getting Started - Tutorials
    • Administrator's guide
    • Features
    • Requirement Yogi for Jira
    • RY Testing and Compliance
    • Integrations
    • APIs
    • Release notes
      • Compatibility matrix
      • Release 1.12 – RY Testing & Compliance
      • Release 2.0 – Excel import
      • Release 2.1 – Ambitious bugfixes
      • Release 2.2 – Change the queue implementation with Jira
        • Release notes 2.2.5 for Jira
      • Release 2.3 – Jira issue creation and traceability matrix
      • Release 2.4 – Improvements to the search
      • Release 2.5 – Public API, ReqIF and queue in Jira
      • Release 2.6 – Library upgrades
      • Release 3.0 – Estimates
      • Release 3.1 – Minor removals (Guide)
      • Release 3.2 – Public Descriptions
      • Release 3.3 – New logos
      • Release 3.4 – New queue and new browser technology
      • Release 3.5 – New indexing engine
      • Release 3.6 – New Excel import
      • Release 3.7, 3.8, 3.9, 3.10, 3.11 – Major compatibility upgrades
      • Release 4.0 – Requirement types
      • Release 4.1 – Comparison tool for the Indexing v2 upgrade
      • Release 4.2 – New UI for the search / reports screens
      • Release 4.3 – Performance improvement for Jira fields in the traceability matrix
      • Release 4.4 – History
      • Notes about Confluence 10 and Jira 11
      • Evolutions
    • Archives (Legacy Features)
      Calendars
    You‘re viewing this with anonymous access, so some content might be blocked.
    {"serverDuration": 10, "requestCorrelationId": "7a51e5100c9c4c9aa776c972eb0b3ea0"}