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 (Cloud)
Results will update as you type.
  • Getting Started - Tutorials
  • Best Practices
  • Administrator's guide
  • Features
  • Requirement Yogi for Jira
  • Testing your requirements - Best practices
  • Integrations
  • REST APIs (Cloud)
  • Release notes
    • October 2025
    • September 2025
    • August 2025
    • July 2025
    • June 2025
    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • 2024
    • 2023
    • 2022
      • October 2022
      • July 2022
      • June 2022
      • May 2022
      • April 2022
      • March 2022
    Calendars
You‘re viewing this with anonymous access, so some content might be blocked.
/
May 2022
Updated Apr 05, 2023

    May 2022

    May 30th 2022

    • (Jira) Remove the "Deprecated" label on the custom field, rename it "Info" and point to the changelogs. We'll keep working on this custom field, our intent is to make it non-editable, but making it possible to perform JQL searches on it.

    May 27th 2022

    Added

    • When viewing a Confluence page, a new indicator (in the byline section) displays page's indexation status and a shortcut to display the transformation wizard

    May 23rd 2022

    • (Jira) The icons at the top of the Jira Issue Glance were changed,

    • (Jira) Bugfix: When a customer didn't have a custom field, they couldn't edit the Issue Glance,

    • (Confluence) The icons at the top-right of the single-requirement view, were changed (view & edit icons, and moved upwards),

    May 20th 2022

    Changed

    • (Jira) The requirement links now also take the space into account when adding a requirement.

    • (Jira) Major We've deprecated the "Custom Field" and implemented a text input similar to the way the custom field behaved, but not limited to 255 characters which will allow users to have more requirements linked to an issue (Notably when the requirement keys are long).

    Removed

    • (Jira) We've deprecated the Requirement Yogi custom field as it is no longer necessary.

    May 5th 2022

    Fixed

    • Fixed an issue preventing users to see the dependencies in the traceability matrix when going over 200 dependencies. Users can now see dependencies as long as there is less than 100 dependency per requirement.

    {"serverDuration": 35, "requestCorrelationId": "841034f87be045d0a7db03820ff75316"}