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.
/
Traceability matrix
Updated Jul 22

    Traceability matrix

    The traceability matrix is the most powerful screen of Requirement Yogi.

     

    Learn the basics of the Requirement Traceability Matrix in this quick tutorial:

    https://www.youtube.com/watch?v=1xTzI_560z0

     

    At the beginning, there is a list of requirements

    We recommend adjusting the search query to only display requirements you are interested in. For example, if you want to filter on the prefix "REQ-", use: key ~ 'REQ-%'.

    Add columns to your report

    You can add columns using the cog menu:

    You can end up with the properties of each requirement. Note the "tree view" on the left, which lets you drill down into requirements.

    Connect to Jira

    If you have requirements attached to Jira issue, they can be included:

    Of course, each Jira field can be displayed in the matrix in Confluence:

    All of these options are available using the cog menu:

    And if you Jira issues are linked to Jira issues:

    Save your report

    Click on the save button to save your matrix for later, this will also allow you to add it in a Confluence page ( RY ReportsPreview )

     

    Choose a name, and the permissions

     

    Find all your matrices in the Reports tab

     

    This matrix can really gather a lot of information, and we recommend using it a lot.

    Embed the matrix in a Confluence page

    If you want to export your report to PDF, or add it into a document with paragraphs and more details, it is possible to embed live matrices in Confluence pages.

    • First, save your matrix.

    • Then click on 'Insert as a macro', or copy the URL.

    • Paste that link into a Confluence page, and update your page.

    • You’ll be able to get updated information from your requirements in that Confluence page.

    Saved Traceability Matrix.png
    Insert the macro.png
    Updated Confluence page.png

    Jira Cache (New in 3.1)

    Jira integration is now faster since you can benefit from a cache, which keeps data for 5 days.

    Type of data cached:

    • Jira issues

    • Epic links

    • Team from Portfolio

    • XRay data

    • Zephyr data

    The user can empty their cached data using the checkbox next to the "Get data from Jira" existing checkbox.

    Limitations

    • We don't have calculations yet. You can't display the percentage of children in a given status, for example. It can't be used to display % coverage, for example.

    • We don't have filters,

    • We may not have all Jira fields, but we've already developed renderers for Xray fields (Xray integration with Requirement Yogi) and we could do it for you too.

    We practically have everything else.

    List of supported Jira fields in the traceability matrix

    Type

    Field

    Type

    Field

    Basic fields

    status
    issuetype
    labels
    priority
    components
    versions
    fixVersions
    project (name and key)
    description
    summary
    subtasks
    issuelinks
    Stories in Epic

    All fields with types

    Numbers
    Strings
    Booleans

    (Datetime and datepickers are among the custom fields)

    Custom fields (Atlassian)

    com.atlassian.jira.plugin.system.customfieldtypes:labels
    com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons
    com.atlassian.jira.plugin.system.customfieldtypes:select
    com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes
    com.atlassian.jira.plugin.system.customfieldtypes:multiselect
    com.atlassian.jira.plugin.system.customfieldtypes:textarea
    com.atlassian.jira.plugin.system.customfieldtypes:textfield
    com.atlassian.jira.plugin.system.customfieldtypes:datetime
    com.atlassian.jira.plugin.system.customfieldtypes:datepicker
    com.atlassian.jira.plugin.system.customfieldtypes:float
    com.atlassian.jira.plugin.system.customfieldtypes:url
    com.pyxis.greenhopper.jira:gh-epic-link (Jira Software - Sprint)
    com.atlassian.teams:rm-teams-custom-field-team (Portfolio - Team)

    Custom fields (Other vendors)

    com.xpandit.plugins.xray:tests-associated-with-test-plan-custom-field
    com.xpandit.plugins.xray:test-plans-associated-with-test-custom-field
    com.xpandit.plugins.xray:test-sets-custom-field
    com.xpandit.plugins.xray:test-plan-custom-field
    com.xpandit.plugins.xray:test-set-status-custom-field
    com.xpandit.plugins.xray:test-plan-status-custom-field
    com.xpandit.plugins.xray:test-execution-status-custom-field
    com.xpandit.plugins.xray:test-run-status-custom-field
    com.xpandit.plugins.xray:testexec-tests-custom-field
    zephyr (basic fields)

     

    {"serverDuration": 19, "requestCorrelationId": "1d0a3c78553b477eaa3524d62df6cb6b"}