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
    • Installation Checklist
    • RY Champions
    • Cleanup Tasks
    • Rename requirements
    • Key suggestions
    • Migrating from DC to Cloud
    • Data residency
    • Limitations
    • IPs and domains used by Requirement Yogi
  • Features
  • 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.
/
Key suggestions
Updated Jun 11

    Key suggestions

    When defining your first requirements in Confluence, we register those keys so we are able to suggest new requirements, and prevent you from reusing the same keys.

    • Suggestions based on your input, other requirements in the page, and across your space and variants.

    • For example, with the requirement CAT-002-REQ-004, we now suggest CAT-002-REQ-005 and CAT-003-REQ-001.

    • If you want to administrate key suggestions, you can go to Requirement Yogi > Manage > Key Suggestions.

      • Delete key suggestions,

      • Edit and reset key suggestions.

    RY Key suggestions.png
    RY Key suggestions admin.png

    Frequently asked questions

    • I’ve just entered a requirement, and it’s still showing up in the suggestions:

      • It may take a couple of seconds for us to receive the Confluence Draft of the page, with the new requirement you just created. If you want to make sure the requirement suggested is correct, click on the refresh button in the input box.

     

    Please feel welcome to give us feedback on our support!

    {"serverDuration": 12, "requestCorrelationId": "adda82efdbca4899bf4d74615e948883"}