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
  • RY Testing and Compliance
  • Integrations
  • APIs
  • Release notes
    • Compatibility matrix
      • API Versions (Confluence-Jira communication)
    • Release 1.12 – RY Testing & Compliance
    • Release 2.0 – Excel import
    • Release 2.1 – Ambitious bugfixes
    • Release 2.2 – Change the queue implementation with Jira
    • Release 2.3 – Jira issue creation and traceability matrix
    • Release 2.4 – Improvements to the search
    • Release 2.5 – Public API, ReqIF and queue in Jira
    • Release 2.6 – Library upgrades
    • Release 3.0 – Estimates
    • Release 3.1 – Minor removals (Guide)
    • Release 3.2 – Public Descriptions
    • Release 3.3 – New logos
    • Release 3.4 – New queue and new browser technology
    • Release 3.5 – New indexing engine
    • Release 3.6 – New Excel import
    • Release 3.7, 3.8, 3.9, 3.10, 3.11 – Major compatibility upgrades
    • Release 4.0 – Requirement types
    • Release 4.1 – Comparison tool for the Indexing v2 upgrade
    • Release 4.2 – New UI for the search / reports screens
    • Release 4.3 – Performance improvement for Jira fields in the traceability matrix
    • Release 4.4 – History
    • Notes about Confluence 10 and Jira 11
    • Evolutions
  • Archives (Legacy Features)
    Calendars
You‘re viewing this with anonymous access, so some content might be blocked.
/
API Versions (Confluence-Jira communication)
Updated Jul 31

    API Versions (Confluence-Jira communication)

    System administrators only

    This page is not generally useful to end-users.

     

    As part of making Jira and Confluence communicate, we account for the possibility that customers may be blocked with an ancient version of either side, for many reasons. Therefore, we’ve introduced the concept of “API Versions”:

    • Some features are disabled if the other side isn’t aware of newer API versions,

    • The upgrade protocol is automatic,

    • The API Version can be set manually by customers, if a newer API version doesn’t work.

    API Version

    Version

    Confluence version

    Published on

    API Version

    Version

    Confluence version

    Published on

    v0-8

    Unsupported

     

    2021-02-17

    v9

    2.6.3

    7.4-7.12 EOL

    2021-04-25

    v10

    2.6.5

    7.4-7.12 EOL

    2021-05-24

    v11

    3.1.1

    7.4-7.17 EOL

    2022-03-11

    v12

    3.4.12

    7.13-8.0 EOL

    2022-12-29

    v13

    3.10.9

    7.19-9.1 EOL

    2024-10-02

    v14

    3.10.14

    7.19-9.1 EOL

    2024-11-15

    v15

    3.11.0

    8.5-9.5

    2024-11-25

    v16

    4.2.12

    8.5-9.5

    2025-06-19

    Newer versions

    This list is not automatically updated, please refer to your administration console for more information.

    Our tip:

    • Just let Requirement Yogi automatically upgrade to the latest API version,

    • Keep Requirement Yogi upgraded on both sides, it’s always better[1]. To this effect, we maintain 2 years of compatibility with the LTS versions of Confluence and Jira.

    • Keep Confluence and Jira updated. We wish most of you would move to the latest LTS version!

     

    [1] Our latest version benefits from upgraded libraries (for vulnerabilities) at the time of publication. So, staying on older versions may mean you are using vulnerable libraries.

    [2] It seems Atlassian makes one LTS version per year (“Long-term support”), with a 2-year window. Our statistics:

    • 2% on the latest version of Confluence.

    • 16% on intermediate versions,

    • 36% on the latest LTS (<1 year old) ← Best choice ,

    • 46% customers stay on 2-years-old LTS ← Beware of dropping out of the support window!

    So, 46% customers feel safer running on the oldest possible software, but most vendors drop support at the end of the 2-year window, and they need to upgrade Confluence in emergency. Which is much less safe. Solution: Upgrade once per year, to the latest LTS!

    {"serverDuration": 12, "requestCorrelationId": "6e6b15b138c8431bae8c686a12f1f210"}