Versions Compared

Old Version 8

changes.mady.by.user Bernhard Doleschel

Saved on

compared with

New Version 9

changes.mady.by.user Bernhard Doleschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section Column
width70%
Baseline Concept

Overview

A baseline represents the state of a set of requirements at a specific point in time.


This could be for example a milestone, the creation of

A baseline might represent a project milestone, such as an important review or a new release

or a new branch

.


Baselines serve as basis for later comparison and measuring of changes within requirements.In Requirements for JIRA baselines can be created any time

Baselines are used to identify changes in a set of requirements.

Baselines can be created at any level of a

projects

project hierarchy.


A baseline contains the state of

all requirements and

each requirement, including child requirements, starting from the selected folder

the baseline was created on

and extending through all

subsequent

folders in that hierarchy.


The state of an issue consists

of all fields

of the

issue and their corresponding values.
The state complies to the revision of the issues

values of the fields included in the R4J Detail View at the time the baseline

was View all baselines from every project

is created.

Baselines can be compared after creation.
A comparison always consists of two baselines.
Also the baselines do not necessarily have to be created on the same project.

Column
width30%
Panel

On this page:

Table of Contents
indent15px

How to use baselines

Create a new baseline

  1. Switch to the tree-view of the project you want to create the baseline on
    1. either click on Requirements in the main navigation bar and select a project from Current Project or Recent Projects
    2. or Select Requirements > View All Projects from the main navigation bar and select a project from the list
  2. Right click the folder from the project tree you want to create the baseline on
  3. Select Create Baseline
  4. Enter a name and a description for the new baseline and click Create
Info

Tip: Baselines can be created through filtered tree results!

View existing baselines

Info

Thanks to Requirements Reuse, baselines may contain requirements from different projects.

Table of Contents

Usage

Purpose

How to invoke

Create baseline

Right click the desired folder for the baseline in the project tree view, select Create Baseline, enter the name and description of the new baseline and select Create.

Info

If a tree filter is in effect when a baseline is created, the resulting baseline only contains the items matching the filter.

View all baselines

Select Requirements > View All Baselines from the

main navigation bar

R4J dropdown. The resulting table lists the baselines in all R4J projects. The table can be filtered and reordered by column.

View baselines

from

in a

specific

project

Switch to

Select Baselines in the project tree

-

view. The resulting table of

the project you want to view a baseline from
  1. either click on Requirements in the main navigation bar and select a project from Current Project or Recent Projects
  2. or Select Requirements > View All Projects from the main navigation bar and select a project from the list
  • Click on the Baselines button in the top right corner
     
    • Info

    For every issue the revision history located in the issue detail view also states the number of baselines including this issue.

    Select a baseline from the list to display it's content

    With the buttons above the baseline content you can

    • Filter the displayed fields of all issues contained in the baseline
    • Collapse all contained issues
    • Export the baseline content to XML or Excel
    • Add a Signature for the baseline (Note that submitted signatures are irrevocable)

    Edit a baselines description

    1. Switch to a baseline view of your choice
    2. Click on the Edit icon next to the baseline you want to edit
    3. Enter a new description and click Edit

    Delete a baseline

    1. Switch to a baseline view of your choice
    2. Click on the Delete icon next to the baseline you want to delete
    3. Click Delete to delete the baseline

    Compare Baselines

    1. Switch to a baseline view of your choice
    2. Select the two baselines you wish to compare
    3. Click Compare selected baselines

    Baseline Comparison Reference

    Comparison Content

    A baseline comparison lists all issues from the compared baselines.
    For every issue all fields are listed and the values from the particular revision of the issue in each of the two baselines are compared.
    If the value of a field has changed between two baselines that field is highlighted in color.

    If an issue is part of only one baseline the entire issue is highlighted in color. 
    For the baseline that contains the issue the values of all fields are displayed. 
    For the other baseline an indication is displayed, that the corresponding issue isn't contained.

    Filtering Comparison Results

    Quick Filters

    It is possible to filter the issues from a baseline comparison using quick filters. 
    To apply a quick filter click on the corresponding button in the baseline comparison.
    To remove a quick filter click the button again.

    The following quick filters can be applied:

    Only Changed Issues
    Only issues that are contained in both baselines and have changed between the two baselines are displayed in the comparison.
    It doesn't matter whether the left or the right baseline contains the newer revision of an issue and therefore the changes

    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. Baselines from different projects can be compared.

    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.

    View baseline details

    In the list of baselines, select a baseline to open the Baseline Details. The buttons above the details allow you to perform the following actions:

    • Select the fields to be displayed.

    • Expand or collapse the details of the contents of a baseline.

    • Export the content of a baseline to XML or Excel.

    • Add a signature to a baseline. See Baseline Signatures.

    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.

    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 fields displayed in the comparison can be changed by selecting Display Fields and selecting or deselecting fields in the list.

    The following quick filters are provided:

    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.

    Filter Fields

    It is possible to select the issue fields displayed in the comparison.

    Click on the Filter Fields button located in the top right corner to open a list of fields available.
    By default all issue fields are displayed. To remove issue fields from the comparison uncheck the corresponding entry in the list. 

    Click on Clear selected items to uncheck every entry of the list.

    Click on Filter to apply the selection, Reset to reset the selection back to the default values and Cancel to revert the changes.
     

    InfoNote that the quick filter Only Changed Issues, applied after filtering issue fields, will only consider the visible issue fields.
    This means that although an issue might have changed between the selected baselines, it won't be displayed with the quick filter applied if the fields that received those changes aren't visible. 

    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.