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
    • Calculations
      • Use cases
      • Calculation syntax
      • Calculation macro
    • 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
  • Testing your requirements - Best practices
  • Integrations
  • REST APIs (Cloud)
  • Release notes
    Calendars
You‘re viewing this with anonymous access, so some content might be blocked.
/
Use cases
Updated Nov 20, 2024

    Use cases

    Estimate the cost of a requirement

    1.2 * (@Man\ days * 150 + ext@Manufacturing\ Cost)

    Here, we see that the result for requirement AA-003 is marked as error because the property @Man days used in the calculation is not a valid number.

    Estimate the total cost of a parent requirement

    SUM(ext@Cost, child)

    Detect when a parent requirement is over budget

    SUM(ext@Cost, child@Uses) > @Budget

    Detect when parts composing an assembly are too heavy

    SUM(@Weight, child@Refines→child@Uses) > @Max\ weight

    Here, we see that the result for requirement AA-003 is marked as error because the property @Weight used in the calculation is not a valid number.

    Measure the coverage of a requirement

    Percentage per relationship name

    100 * IF(COUNT(child) = 0, 0, COUNT(child@Refines) / COUNT(child))

    Screenshot 2024-03-18 at 10.05.54.png

    Here, this will tell you out of all children of BR, how many of them use the relationship ‘@Refines’, this is why it is necessary to specify a relationship name.

    Does the requirement have a dependency?

    parent@Refines->(key ~ 'BR-%')

    Visual Editor query.png

     

     

    Advanced Editor query.png
    Result of the query.png

    To know if a requirement has a parent or child with the relationship ‘@Refines’ with the key ‘BR-%’.

    • This will give you a true or false answer.

    • It can also be used with the child relation, and key ~ '%'

    Measure the Test Coverage of children requirements

    PERCENT(DISTINCT(child@Refines), ext@Test\ result = true)

    Test Coverage of children requirements.png

    Percentage of children requirements with relationship Refines, having an external property "Test result" completed

    {"serverDuration": 12, "requestCorrelationId": "36c4010a3cb64a20bcf71b3c9dec8c04"}