...
| Table of Contents | ||||
|---|---|---|---|---|
|
New features
| Note |
|---|
Note to administrators |
| Note |
tl;dr
|
| 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.
|
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.
...
Space administrators can view everyone’s private reports and reassign them, in case an employee leaves the company.
...
Other changes
Jira issue titles are not cached in Confluence anymore
https://requirementyogi.atlassian.net/browse/RY-1312
We used to copy the title of the Jira issue in Confluence, but that triggers issues about the permissions on those Jira issues. Since the OAuth / application links work well, we now only keep the issue key, and retrieve the Jira issue with the permissions of the current user.
Impact on the traceability matrix: The ability to display the Jira summary field in the same cell has disappeared. Customers will have to display a separate column, containing the Jira issue summary.
Properties in the traceability matrix: Resolved the “large menu” issue
...
Users with a lot of properties had difficulties when inserting properties in the matrix, since the page snapped up and down when displaying the properties.
We’ve created a dialog box, so users can select their properties using the autocomplete.
“Public descriptions” are deprecated
| Status | ||||
|---|---|---|---|---|
|
“Public descriptions” is an old mode 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.
Go to https://www.requirementyogi.com/manage-profile/ to subscribe.