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
    • Properties & Dependencies
    • Requirement Types
    • Search Syntax
    • Traceability matrix
    • Estimates and External Properties
    • Baselines and versioning
    • RY Reports
    • Dependency Matrix and Coverage
    • Word Import
    • Excel Loop: Re-import requirements after customer's comment or validation
    • Excel Import: Add external requirements to RY
    • Key Suggestions
    • Renaming Requirements
    • Blueprints and Templates
    • History
  • Requirement Yogi for Jira
  • RY Testing and Compliance
  • Integrations
  • APIs
  • Release notes
  • Archives (Legacy Features)
    Calendars
You‘re viewing this with anonymous access, so some content might be blocked.
/
History
Updated Sept 25

    History

    New feature in 4.4.0

     

    Requirement Yogi can store every change.

    The feature is pretty straightforward: After modifying requirements, go to the space administration, and list the changes:

    Screenshot 2025-09-18 at 16.35.54.png
    History in the space administration

    Searching using criteria

    You can review the history of modifications for a user or for a specific requirement. Fill in the search fields:

    Screenshot 2025-09-18 at 16.39.16.png

    This field is the record ID. For example:

    • J-026: Search for any record named J-026

    • SJ/J-026/current: Search with the space and current baseline,

    • SJ/J-026/1: Search for the requirement in baseline 1.

     

    Types of records

    In version 4.4.0, we only save the details of requirements.

    Identifying the author of a change

    Since Confluence live pages can be modified by several collaborators concurrently, only one author will be remembered for any change. Also, if a previous job failed or an event was missed, changes may seem to be attributed to the next person, when the next person only reindexed the page. Please always consider this limitation when identifying authors of a change.

    Permissions

    The history is visible to space administrators and global administrators only, and owners of objects when relevant.

    Notes to administrators

    In 4.4.0, the history needs to be activated manually.

    Screenshot 2025-09-18 at 16.24.37.png

    See: History - Administrator's guide.

     

    We recommend administrators to tune the settings according to the performance of their environment. Please refer to the administrator’s guide for more details.

    {"serverDuration": 33, "requestCorrelationId": "65fd893b9e524ca3926c509cb71fd7c6"}