Contents of the release
Like in the Cloud, we’re adding support for “Champions” in Data Center.
-
Champions are functional experts for Requirement Yogi,
-
Champions may, together, take decisions regarding the configuration,
-
Global administrators can delegate some configuration to Champions,
-
Global administrators keep the system administration decisions (connection with Jira, etc.).
Other contents of the release:
-
Support for
<,<=,>,>=andIN()in the search syntax, like on the Cloud, -
Support for the Expand macro,
-
Display the EULA in the administration.
The Champion Center
We’re introducing a new way for the global administrators to delegate the functional administration of Requirement Yogi. We call them “Champions” of Requirement Yogi. Here is what they can see:
The group of champions is empty by default, and can be designated in the administration:
Admin-level tasks remain at the global level. Here are examples:
|
Activity |
Space-admins |
Champions |
Global admins |
|---|---|---|---|
|
Upgrade tasks |
|
|
|
|
Designate champions |
|
|
|
|
Setup the Jira integation |
|
[1] |
|
|
Logging |
|
|
|
|
Activate the license & EULA |
|
|
|
|
Uninstallation wizard |
|
|
|
|
Backup and import tools |
|
[1] |
|
|
Manage Requirement Types |
|
|
|
|
Manage external properties (type, name) |
|
|
|
|
Manage the queue
|
|
|
|
|
Manage the history |
|
|
|
|
View usage metrics |
|
|
|
|
Set global limits |
|
|
|
|
Set permissions
|
|
|
|
|
Choose the Indexing Engine |
|
|
|
|
Manage a space |
|
|
|
[1] We’re studying whether it would be reasonable to delegate those features to Champions.
Notes for system administrators
-
Confluence 9.2 wil be end-of life in December 2026. Confluence 10 is already 45% of our installed base (according to Atlassian). Please upgrade to Confluence 10.2 as per our Compatibility matrix,
Risk assessment
-
The only major changes on this release are the search syntax, the new permissions for the champions, and the rewrite of the front-end for some part of the global administration.
-
In case of difficulty, it is possible to downgrade the plugin to 4.5.x. To do so, uninstall the plugin (the data won’t be deleted), download the older version from the Atlassian Marketplace and install it by uploading it in UPM.
Medium Front-end issues are possible, and would be easily corrected.