Page Comparison

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.

The new algorithm stores the last generated key, a bit like a sequence in SQL. It means suggestions should be extremely fast (we've seen 200ms instead of 25s in some cases).

Edge cases:

• 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-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.(Writing...)

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:Image Added

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):

• There is a progress bar,
• The requirement count is approximate when refreezing from another baseline, because we are not able to calculate in-memory the difference between the old baseline, and the added/removed requirements.
• We don't suggest to add dependencies automatically.
• We require to have a record in the database for this baseline,
• For "instant baselines" (baselines created about a single page in Confluence), we used to create an associated page to summarize the baseline, and we don't do that anymore. If you need this associated page, then create the baseline using the search and the wizard.

Example with the Baseline blueprint:

Example with the baseline wizard:

Baselines: We don't suggest the dependencies anymore