Operations
Purpose | How to invokeAction | ||||||||
|---|---|---|---|---|---|---|---|---|---|
Create baseline | Right click the desired folder for the baseline in the project tree view, select Create/Add > Create Baseline, enter the name and description of the new baseline and select Create.
| ||||||||
View all baselines | Select Requirements > View All Baselines from the easeRequirements dropdown. The resulting table lists the baselines in all easeRequirements projects. The table can be filtered and reordered by column. | ||||||||
View baselines in a project | Select Baselines in the project tree view. The resulting table of baselines can be filtered and reordered by column. | ||||||||
Compare baselines | In the list of baselines, select the two baselines you wish to compare and select Compare selected baselines. See section Baseline Comparison for more information. | ||||||||
View baseline details | In the list of baselines, select a baseline to open the Baseline Details. The baseline details are displayed from oldest to latest issue. The buttons above the details allow you to perform the following actions:
| ||||||||
Edit baseline name and description | In the list of baselines, select the edit icon. | ||||||||
Delete baseline | In the list of baselines, select the delete icon. |
Baseline Comparison
| Anchor | ||||
|---|---|---|---|---|
|
A comparison of two baselines lists every requirement that is in at least one of the baselines. In the case of requirements that exist in both baselines, the values of the fields in each revision are displayed side by side. Fields with different values in the baselines are highlighted. In the case of requirements that exist in only one baseline, all fields in the revision are highlighted. An indication that the requirement is missing in the other baseline is displayed.
The option “Compare as Tree” provides the side-by-side comparison of two baselines in tree view. The highlights and indications of differences in issue and field values work in the same way as in the list view.
| Status | ||||
|---|---|---|---|---|
|
The fields displayed in the comparison can be changed by selecting Display Fields and selecting or deselecting fields in the list.
You can enable the rendering of wiki markup in text fields by selecting Visual.
Text diffs, the red and green highlight on exact character changes, are disabled for RTE fields when using visual mode. Images are displayed with a placeholder for past revisions and baselined revisions, since Jira and easeRequirements do not track attachment history.
The following quick filters are available for comparing baselines:
Only Changed Issues | Only requirements that are contained in both baselines and have different values for at least one field are listed. Only the fields included in the list of displayed fields are taken into consideration when determining if a requirement has changed. That is, if the value of a field is different, but the field is not included in the current setting of Display Fields, the requirement is not regarded as being changed. |
Only on Left Side | Only issues that are contained exclusively in the left baseline are displayed. |
Only on Right Side | Only issues that are contained exclusively in the right baseline are displayed. |
Baselines from different projects can be compared, but in general comparing baselines in different projects is not useful, since the two sets of items do not overlap. However, if you are practicing Requirements Reuse, comparing baselines in different projects can be valuable. For example, suppose you have a “catalog” project, consisting of standard requirements. A new project starts by including all the requirements in the catalog. A comparison of baselines in the two projects would now show no differences. As the project progresses, it replaces standard requirements with project-specific copies when the needs of the project diverge from the standard. A comparison of baselines in the two projects would now display exactly those copies and hence show how the project has diverged from the standard catalog.
Baseline Signatures
Baselines can be electronically signed. For example, a project may require that the members of its Change Control Board review the baselines of important milestones. Baselines are provided to the members via links. Each member is expected to sign off with a digital signature and mandatory free text comment (e.g. approved, rejected).
Once a signature has been submitted it cannot be changed or revoked.
Baseline Tree View
This view displays the issues and pages in the baseline as a tree, which allows better visualization and overview of the items in the baseline.
Functions in this view are limited to the following:
Select an issue, folder, or page to view its baselined details.
Issue details include all baselined fields under “Details“ section, a rendered “Description“, and a comma-delimited list of “Attachments“ and “Issue Links“.
Folder details only include the folder name and statistics.
Page details only include the page version.
Context menu in the Root Folder to “Show current in issue navigator“ redirects to the Jira issue navigator showing the issues included in the baseline.
Switch between the Baseline Flat List View and the Baseline Tree View.
Add a signature to a baseline. See Baseline Signatures.
There are limitations to older versions of easeRequirements where positions and paths of tree items are not stored in the baseline. These cases are handled with a default display, where items without positions are displayed in the tree from latest to oldest, items without paths are displayed in the root folder and folders sorted alphabetical.