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
    • Configuration
    • Maintenance guide
    • Limitations
    • Migration to the Cloud
    • Requirement Yogi Cloud vs Data Center
    • Backup, import and export of Requirement Yogi data across Confluence and Jira instances
    • Database schema
    • Changing Applinks
    • Performance
    • Copying, Splitting and Moving pages
    • Choosing the indexing engine
    • Notifications
    • Data Center SLA / Escalation process
    • History - Administrator's guide
  • Features
  • 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.
/
Configuration
Updated Apr 03, 2023

    Configuration

    Requirement Yogi has very little configuration. If you're looking for information on how to organize your requirements, take a look at our videos or go straight to the onboarding.

    Configuration in Confluence

    Configuration in Confluence

    There is no specific configuration. There is an administration screen to gather logs, in case you need to raise a bug report

     

    Configuration in JIRA

    Configuration in JIRA

    You must configure the Applinks. Go to Requirement for Jira documentation.

     

    • You may configure the link types.

      • To search for this administration screen, use the shortcut 'gg', then search for 'Requirement Yogi'.

      • The administration screen

    Global Synchronization

    Global Synchronization

    JIRA issues reflect the links at the time of creation. If you want to update links (for the title, or if the requirement moved or was deleted), please click "Synchronize" on the given issue. Alternatively, you can request JIRA to update all Requirement Yogi links, although it may be long depending on the number of issues you have and the quantity of requirements to update.

    To apply the global synchronization, go to JIRA Administration → Issues → RY Synchronization.

    The synchronization then happens in a background task and you'll see the details as they come in:

    System properties

    Normally unnecessary, it is possible to override some settings using system properties:

    System property

    Default value

    Definition

    System property

    Default value

    Definition

    requirementyogi.sql.escape.entity.open

    The character detected by RY

    The opening character to escape column names in ActiveObjects SQL.

    requirementyogi.sql.escape.entity.close

    The character detected by RY

    The closing character to escape column names in ActiveObjects SQL.

    requirementyogi.jira.limit

    3000

    The number of Jira issues that we attempt to fetch in a single query (ex: for the traceability matrix)

    requirementyogi.jira.batch.size

    100

    The number of Jira issues per query. 

    requirementyogi.applink.timeout (in Jira or Confluence)

    30s + 0.1s per item

    The timeout (in ms) for any connection between Jira and Confluence using the application links.

     

    {"serverDuration": 35, "requestCorrelationId": "ac7b242fc6bd40a4a56c616b4c294a6b"}