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
  • Requirement Yogi for Jira
    • Custom field for Requirement Yogi
    • Jira links
    • Jira Issues Bulk Creation from requirements
    • JQL Syntax
    • How to import Jira issues in CSV using the Yogi custom field?
    • RY for Jira Configuration
  • 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.
/
Requirement Yogi for Jira
Updated Jul 09

    Requirement Yogi for Jira

    To use all Jira connected features, make sure you download the Requirement Yogi for Jira app first.

     

     

     

    How to set up the integration?

    • Set up the Application Links between Jira and Confluence,

    • Set up Entity Links between a Jira project and a Confluence space (or several),

    • Important Go to the administration and set the credentials in both products (since 2.2 for Confluence and 2.5 for Jira).

    • Go to the Requirement Yogi for Jira configuration page for more explanations

    What does the integration look like in Jira?

    A Requirements panel on Jira issues:

     

    A custom field, if you choose to configure it instead of the panel:

     

    The dialog to add links on an issue:

     

    What does the integration look like in Confluence?

    The glorious Jira bulk issue creation:

     

    And of course, Jira issues appear in the popup as dependencies, and in the traceability matrix.

     

    More about the Custom Field

    Using the custom field is optional. All requirements can be displayed in the "requirements" panel, but some customers prefer using the custom field, which makes it possible to:

    • Make requirements visible in the REST API,

    • Make requirements visible in the XML API,

    • Make the field visible and mandatory on the Create Issue screen.

    If interested, see more details on Release notes 2.2.5 for Jira

    JQL function

    The JQL function to search for issues with Requirement Yogi links is described on this page: JQL Syntax.

     

    Related content

    • Custom field for Requirement Yogi
    • Jira links
    • Jira Issues Bulk Creation from requirements
    • JQL Syntax
    • How to import Jira issues in CSV using the Yogi custom field?
    • RY for Jira Configuration
    {"serverDuration": 11, "requestCorrelationId": "a19863d12a4c4699bf9fcdf67ac0c185"}