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
Requirements
Yogi Status & Dropdown
Yogi Calculations
You‘re viewing this with anonymous access, so some content might be blocked.
/
Release 3.5 – New indexing engine
Updated Jan 04

    Release 3.5 – New indexing engine

    • 1 Note to administrators
    • 2 CCMA and JCMA - Migrations to the Cloud
    • 3 A new indexation engine
    • 4 Key Suggestions
    • 5 Bugfixes

    Note to administrators

    Important

    After installing 3.5.0, do not downgrade to 3.4.x. We have changed the format of property names, and it is possible to enter data in 3.5.0 that is interpreted with an XSS in 3.4.x.

    CCMA and JCMA - Migrations to the Cloud

    With this version, we’ve finally made it possible to migrate to the cloud using a simple click!

    Go to Migration to the Cloud for more details.

    A new indexation engine

    Don’t worry, existing customers keep the old engine. However, they are encouraged to switch to the new one and give us feedback about the new rendering.

    • The version 2 is better since we don’t make the users wait while saving a page, we just post the event in a queue and the requirements are processed later on.

    • The version 2 is recommended for Data Center instances.

    • We want to make the version 2 the principal engine in the future, so please give us feedback about the rendering. We’ll certainly make it the default in the future (RY 4.0).

    Read more about choosing the indexing engine on this page.

    Key Suggestions

    RY-1079: Key suggestions: Add an option to "isolate spaces" for key generationClosed

    Administrators can:

    • Lock keys to prevent users from creating random requirement keys,

    • Use global keys instead of space keys,

    • Define different settings for some of the spaces.

    See Key Suggestions for more details.

    Bugfixes

    More bugfixes will come in 3.5.x iterations, but here are some fixes for 3.5.0:

    • RY-1118: Name the Excel export file after the name of the saved queryClosed

    • RY-1218: Problem during uninstallation, with report macrosClosed

    • RY-1235: The macro "include-page" should render requirements from other spacesClosed

     

    {"serverDuration": 40, "requestCorrelationId": "5baa50d0a35b4ba5a694ee9ed9944ee3"}