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 2.4 – Improvements to the search
Updated Jan 04

    Release 2.4 – Improvements to the search

    This release focuses on the improvement of the seach with Russian characters in property names and values.

    In this release

    Use Russian or most UTF-8 characters in property names, values and in the search. 

    Release 2.4.1

    This is rather a technical release, to check everything works well with some big underlying change:

    • We are now using Javascript/ES6. It shouldn't be visible from the user's point of view but, in case of issue, you can downgrade back to 2.3.3.

    • We support UTF-8 in property names and values! (long-awaited feature) We also support numbers, for example "baseline = 1" is now legal.

    • We've removed the "Email our support from within the app" feature, for GDPR compliance.

    • We've disabled jobs when Confluence was in read-only mode.

    Release 2.4.2

    Minor bugfixes

    Release 2.4.3

    Our change: We index properties differently.

    • Before: We used to let the user search on the HTML of the properties,

    • After: We've split the column between display and search, so what is displayed is the HTML, but what can be searched is the textual content of a value.

    Example: If a property contained a status, the HTML would be something like <span class="status-success">OK</span>, so the search query would be ugly: @Property = '<span class="status-success">OK</span>'



    Stored data for display

    Stored data for search

    Displayed as

    Search query

    Comments



    Stored data for display

    Stored data for search

    Displayed as

    Search query

    Comments

    Before

    <span class="status-success">OK</span>

    (None, it didn't exist)

    OK

    @Property = '<span class="status-success">OK</span>'

    The search was ugly.

    After

    <span class="status-success">OK</span>

    "OK"

    OK

    @Property = 'OK'

    Awesome.

    I hope you understand that this is a major improvement, and will be satisfied with the implementation.

    Other changes:

    • It is not necessary anymore to use quotes around numbers: "baseline = 1" or "page = 2" are valid queries,

    • We've introduced "==" for the strict equality.

    • We've introduced functions, for the moment only one:

      • user("mylogin") returns an object of type User which can only be used when checking mentions in properties, example: @Author = user("mylogin"). Also works with the user's key.



    {"serverDuration": 10, "requestCorrelationId": "80ef5908e235498c935efcca4870d93f"}