Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

Note to administrators

  • Do not downgrade below 3.5.0 after upgrading to 3.5.x or 3.6.x.

  • We’re switching all customers by default everyone to the “Confidential” mode for the “Public descriptions”new mode of integration with Jira (“Public descriptions” is deprecated, “Confidential” is the new normal). Please notify us if this is a problem.

  • We’ve reorganized the tabs in the space, including deleting two tabs (see below),

  • We have a new Excel import, for properties,

  • Traceability matrices don’t display the Jira issue summary by default, users will have to add a new column.

Warning

Advance notice

We would prefer all customers to use Java 11, which has been the default for Confluence 7.13 for two years already.

  • Confluence 7.13 LTS: Not supported anymore (published in August 2021, ships Java 11 by default),

  • Confluence 7.19 LTS: New minimum version for Requirement Yogi, published in July 2022,

  • Confluence 8.0: Drops support for Java 8, published in November 2022,

  • Confluence 8.5 LTS: Published in August 2023.

New tabs for the space

...

  • The tab “Estimates” and “Excel” has disappeared,

  • There is a new tab named “Reports”.

  • There is a new tab “External properties”, which both display external properties and the Excel import for those external properties.

...

“Public descriptions” are deprecated

Status
colourRed
titleImportant
https://requirementyogi.atlassian.net/browse/RY-1305

“Public descriptions” is an old mode which that we don’t like, because we are not sure that customers understand the impact of activating it. Therefore, we are deprecating this mode:

  • Customers since May 2022, who haven’t activated the option, won’t see the option,

  • Older customers will be switched to the new mode by default, “Confidential” descriptions by default. They can switch back, but please complain to us, so we know that you really need this mode.

As a reminder, this is related to the way Confluence integrated in Jira. Before 3.2.0, we used to send the full requirement excerpts to Jira at every update, and display them to anyone in Jira. After 3.2.0, we don’t push to Jira, but rather Jira pulls from Confluence whenever a user views an issue. It has the upside of only displaying requirements with the permissions of the current user.

...

Join the community

We’ve created a mailing list, to tell you about new features, security vulnerabilities, and the community… , and the good news is that those categories are separated.

...