...
Baselines: Synchronization with page titlestitles
Status |
---|
colour | Red |
---|
title | Feature removal |
---|
|
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):
- There is a progress bar,
Status |
---|
colour | Red |
---|
title | Feature removal |
---|
|
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. Status |
---|
colour | Red |
---|
title | Feature removal |
---|
|
We don't suggest to add dependencies automatically.- We require to have a record in the database for this baseline,
Status |
---|
colour | Red |
---|
title | Feature removal |
---|
|
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. Status |
---|
colour | Red |
---|
title | Feature removal |
---|
|
A bug used to allow to create cross-space baselines. It was neither intended nor working properly, and it was removed.
Example with the Baseline blueprint:
...
Baselines: We don't suggest the dependencies anymore
Status |
---|
colour | Red |
---|
title | Feature removal |
---|
|
As seen in the Step 3 above:
...
That's all. We have tried to keep changes almost seamless in 3.1 compared to the version 3.0, and we have removed the minimum, and we hope that we will not inconvenience your users too much. These changes were required to avoid loading large amounts of requirements in memory, and Data Center administrators will certainly appreciate the change.
Baselines: What are the remaining features?
Most of them!
- You can create a baseline from 3 places: From a page ("instant baselines"), from the search, and from the "RY Baseline" blueprint.
- We memorize the requirement, its properties and its dependencies. We create an archived version of each page, so you can always see the requirement in context.
- Concerning dependencies, it is not always possible to navigate properly across baselines, so we recommend to baseline all relevant requirements, or precisely test your intended usecases using examples.
- Images are not baselined. We only save the URL, and the image can be swapped out.
- The links to Jira are not baselined.
- You can refreeze a baseline and add/remove/update requirements. If a requirement is not updated, we don't create an archived version for it, which may be misleading when viewing this requirement again.