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
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 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.
/
Release 3.4 – New queue and new browser technology
Updated Apr 04, 2023

    Release 3.4 – New queue and new browser technology

    Migrating from Requirement Yogi 2.x?

    If you are migrating from Requirement Yogi 2.x, the migration tasks will execute. It is generally fast and seamless, but some customers can experience errors, see Migration to RY 3.0: FAQ for all the details.

    Major change in the browser technology

    We are introducing a new technical library for our front-end, ReactJS. There is no direct benefit for customers and it should not be immediately visible, however this is necessary to keep our product interesting for the developers who work on it.

    important : If there is any screen that isn't loading, please contact us in emergency. We test with all browsers, but production environments are sometimes special.

    For the moment, only the management of the queue in the administration uses this new library.

    New queue, new thread management

    We are now sharing the same code, for the queue between Confluence and Jira:

    • Customers will benefit from a unified UI (There is a new tab in the administration),

    • We have changed the APIs that we are using to launch threads. There should be only 1 thread per queue on the entire cluster (For the moment, 1 thread in Confluence and 2 threads in Jira), and they shut down after 1 minute idle.

    Again, production environments may be different from our staging environments; If, as a system administrator, you notice anything weird, please notify us.

    Troubleshooting

    If you have any trouble:

    • Please use the "Logging" feature in the Requirement Yogi administration, to capture the logs,

    • Then downgrade to Requirement Yogi 3.3.x, to ensure your service is not interrupted,

    • Note that Jira and Confluence don't allow direct downgrades, so you have to first uninstall Requirement Yogi 3.4.0, then upload a the ".jar" file of the version 3.3.11.

    • Then contact us on on our Customer Portal: https://requirementyogi.atlassian.net/servicedesk/customer/portals

    We will be watching for any ticket related to this upgrade.

    List of issues

    See the list of Jira issues here.

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







    {"serverDuration": 20, "requestCorrelationId": "c899d8354c3f448c9e9f4e20b6f7badf"}