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
/
Custom field for Requirement Yogi
Updated Jun 25

    Custom field for Requirement Yogi

    In Requirement Yogi for Jira, you can create a custom field for the Requirement Yogi data. It will allow you to:

    • See the linked requirements in the details of the Jira issue,

    • See the linked requirements in the search, as a separate column,

    • Search for Jira issues associated with a requirement,

    • Have the requirements listed in the REST API of Jira issues.

    Where are the custom fields visible?

    When you have a Requirement Yogi custom field in Jira, the values are visible in the details of tickets, in the search, in the REST API and as a search criteria.

    Jira details.png
    In the Jira detail view
    Search results - as a column.png
    In the search results
    Search criteria.png
    As a search criteria
    REST API for the Yogi custom field.png
    In the REST API

    How to create the custom field in Jira?

    1. Go to the administration of Jira → Issues → Custom fields,

    2. Add a custom field of type “RY Requirement Yogi Links”,

    3. After completing the wizard, come back to the list of custom fields and find the “Configure contexts” menu,

    4. Choose the name of the relationship.

    Adding the Custom Field in Jira.mp4
    How to add the Requirement Yogi custom field

     

    Tips & tricks

    • The data is not stored in the custom field, but in the Requirement Yogi database. Therefore the Requirement Yogi panel and the custom fields represent the same value.

    • The custom field only displays the links of one relationship, while the Requirement Yogi panel on Jira issues display all relationships. If you use several relationships, you will have to create several custom fields. There is no custom field for “all relationships” because there is no room to represent those relationships, on screen or in the REST API.

     

    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.
    {"serverDuration": 10, "requestCorrelationId": "0dcfafa039db4051b2c5eae6e1f535d5"}