...
This release could have been a "bugfix" version, but we've decided to make it a major one to emphasize the removal of 1-2 small features.
Baselines have changed
Continuing our enterprise-scale goals, baselines are now a long-running task, running in the background:
- We had to adapt a few things in the wizards (see "Feature removals"),
- This feature may not feel important for you, but it will allows us to increase the size of baselines in the future by 100-fold or more. We have experiments with baselines of more than 1 million requirements. We keep the limits as usual for now, until the model is polished (equal to the global limit, 12000, configurable).
- The UI has changed a little bit, to display the progress bar, in the 4 places where baselines can be created.
Requirements are generated using an internal table
It should be invisible to users, except from edge cases. Requirement keys used to be suggested by querying the whole database and finding the next gap in requirement keys. It would be very slow, sometimes several seconds.
...
- If a customer removes keys, we won't search for "gaps" between already-assigned keys,
- If you switch the settings between "reassign deleted keys" and "do not reassign", then the table is already populated.
Performance improvements
Those improvements were made in the context of obtaining the Data Center yearly approval.
- https://requirementyogi.atlassian.net/browse/RY-959 Add a maximum size to caches,
- https://requirementyogi.atlassian.net/browse/RY-960 Set caches to replicate through invalidation when possible.
- https://requirementyogi.atlassian.net/browse/RY-964 Reduce all transactions to 5s, particularly in background tasks.
- https://requirementyogi.atlassian.net/browse/RY-970 Autosuggestion of requirement keys: Add a column in the table for the uppercase of the requirement
- https://requirementyogi.atlassian.net/browse/RY-962 Autosuggestion of requirement keys: Store generated keys in a table (as if they were DB sequences) instead of search tables manually. This greatly accelerates key generation.
- https://requirementyogi.atlassian.net/browse/RY-979 Enable administrators to set limits to export sizes, by upgrading to PSEA 1.7 if they want.
Bugfixes
- https://requirementyogi.atlassian.net/browse/RY-968 Fix an error in the viewer for Excel documents,
- https://requirementyogi.atlassian.net/browse/RY-969 In the Jira Bulk Issue Creation, fix an error when clicking "Reapply"
- https://requirementyogi.atlassian.net/browse/RY-972 Search syntax: The NOT keyword is incorrectly applied when used with parenthesis.
- https://requirementyogi.atlassian.net/browse/RY-976 Excel imports: Properties were not imported.
Feature removals
They should be minor, but we want to help you communicate with your users.
Baselines: Synchronization with page titles
Some baselines are linked to a Confluence page, which summarizes it. We used to synchronize the title of the page and the one of the baseline. It was a costly feature in terms of performance because we would have to watch all pages in Confluence. We have removed this synchronization. If you want to rename both a page and a baseline, use the rename feature on the baseline tab:
Baselines: The wizard has changed, with a few steps in the process
In any place where we create a baseline (the wizard, the baseline macro in the blueprint, the instant baselines, and the refreeze):
...
Step 1. Search In the search, click Make baseline. | |
Step 2. Choose the name A title for the baseline will be automatically suggested. | |
Step 3. Check the dependencies This step suggests the dependencies which are Feature removal: We don't display this step when Feature removal: There used to be an "Add" button | |
Step 4. Choose options In the past, the user could choose to freeze now or later; Now, we have 2 options to choose. | |
Step 5. The progress bar Like in the other situations, the "Create baseline" of |
Baselines: We don't suggest the dependencies anymore
As seen in the Step 3 above:
...