Baseline Home

The Baseline Home page provides users with a comprehensive overview of all the baselines created within their project, along with detailed information about the issues linked to each baseline. The page allows users to manage baselines through different lifecycle stages—Open, Committed, and Completed.

Details of Components

• List of Baselines: Explore all the baselines created within the project, categorized by their lifecycle stage: Open, Committed, or Completed. The key attributes like baseline name, ID, status, are displayed in a tile for quick reference.

• Individual Baseline: Each baseline displays essential information such as the baseline ID, description, status (Open, Committed, Completed), approver, and the date it was created. Clicking on a baseline opens the detailed view, where linked issues and baseline metadata are available.

Add Issues Directly to a Baseline

Users can add issues directly to a baseline from the Baseline Details page.

Features Include:

• Search and Select: Search for specific issues and select them for inclusion in the baseline.

• Streamlined Process: Quickly link issues without navigating to another page.

• Visibility of Linked Issues: Once added, the issues are displayed in the issue table below.

Issue Table Behavior

The issue table provides detailed information about the issues linked to each baseline. The table's layout and available actions differ based on the baseline's status:

Open Baseline

In an Open baseline, issues can still be added, modified, or removed. The issue table includes the following columns:

• Issue ID: Displays the current ID of the issue as it exists in Jira. This field is clickable, allowing users to view the issue's current state in Jira.

• Issue Summary: A brief summary of the issue's description, providing a high-level overview of its content.

• Assignee: Shows the current assignee of the issue. If the issue is unassigned, it will display "Unassigned".

• Unlink Button: Displays an Unlink button, allowing users to remove the issue from the baseline while it is in the Open state. Once an issue is unlinked, it will no longer be associated with this baseline.

Committed Baseline

Once a baseline is Committed, it becomes locked, and no further modifications to the issues or the baseline can be made. The issue table in a Committed baseline shows additional features:

• Issue ID: The current Jira state of the issue, which may have been updated since the baseline was committed. Users can click on the Issue ID to view the issue’s current state in Jira.

• Issue Summary: Provides a summary of the issue, displaying its description as of the current Jira state.

• Assignee: Shows the current assignee of the issue. Similar to the open baseline, this column will display either the assignee's name or "Unassigned."

• View Snapshot: Since a committed baseline locks the issues in their frozen state, a View Snapshot button appears. This allows users to view the issue as it was when the baseline was committed, preserving the historical context of the baseline. The snapshot opens a new page that shows the state of the issue (description, assignee, priority, comments, etc.) at the time the baseline was committed.

• Unlink Button: The unlink action is disabled for committed baselines, as the issues in the baseline are locked and cannot be removed or modified. No unlink option will be available, and the Unlink button is hidden or disabled in this state.

Baseline Lifecycle

• Open Baselines: Users can modify, add, or unlink issues within an open baseline. The issue table allows full interaction with the issues until the baseline is committed.

• Committed Baselines: Baselines in the committed state are locked, meaning no further changes can be made to the issues or their relationships. However, users can view the issue snapshots, providing historical data about the issue's state at the time of commitment. The issue table reflects both the current issue state and the snapshot state for comparison.

• Completed Baselines: Once a baseline is marked as complete, it becomes a reference point for future evaluations and reporting. Similar to committed baselines, completed baselines allow users to view issue snapshots, but no further changes are allowed.