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 types
    • Requirements search
    • Requirement dependencies
    • Traceability matrix
    • Report macro: Insert a matrix into a page
    • Coverage
    • Versioning
    • Transformation wizard: Transform your pages
      • Generate keys: Add definition macros in bulk
      • Transform text into requirement keys
      • Transform text into Links
      • Reverse transformation / Transform keys into Links
      • Align your table with Requirement Types
      • Transformations for Vertical tables
      • Headers transformation: assign headers in bulk to all tables in the page
      • Change the variant or space of requirement links
      • Migrate Server macros to Cloud
    • Calculations
    • Linear documents: Manage requirements outside of tables
    • External properties
    • Excel Loop import: Import external properties
    • Configuration macro: Configure properties and documents
  • Requirement Yogi for Jira
  • Integrations
  • REST APIs (Cloud)
  • Release notes
    Calendars
You‘re viewing this with anonymous access, so some content might be blocked.
/
Change the variant or space of requirement links
Updated Feb 01, 2024

    Change the variant or space of requirement links

    When creating Requirement Yogi links, by default, they link to requirements in the same space and the same variant as the page they are inserted in.

    This can cause issues where links are not pointing to the correct space or variant.

     

    You can watch the tutorial for an overview:

    https://youtu.be/4p1B7YwrfO8?si=RIfhU4WhmRTDIPss&t=282

     

    When to use it

    • You have business requirements in a Confluence space "BUSINESS", accessible to your customers, but create your requirements in an other space, restricted to your engineers. When creating Requirement Yogi links, they would have to manually point to the "BUSINESS" space.

    • You are copying a page from a space to another.

    • You are copying a page to create a new variant.

    In all those cases, it would be tedious to manually edit every Requirement Yogi links to all point them to the correct space or variant. We added this transformer to help with this process.

    Using the transformation to change variants or space

    You can access the vertical table transformation from the first step, or the summary step. Like other transformations, you can also save a transformation and reuse it in other pages.

    Selecting the scope of the transformation

    By default, all the requirement links in the page are transformed. Select the tables and column affected by clicking the "Only in tables" radio button.

    Changing the space key

    • Removing the space key will make all requirements selected point to the requirement in the same space as the links

    • Setting the space key allows you to choose which space the links should point to.

    Changing the variant

    • Like space keys, removing the variant will make the requirement links point to the requirement in the same variant as the page they are indexed in.

    • Setting the variant will allow you to choose which variant the links should point to.

    Changing the plugin configuration

    At the summary step before transforming the page, simply click on the rule you want to modify to edit it.

    You can have several rules of the same type with different configurations

    {"serverDuration": 9, "requestCorrelationId": "3fb9406be9fa4846bf63a8cc94ee473e"}