Changes

Overview

The table lists all the change requests managed in the P4SaMD project. Each row represents a P4SaMD Change Request entity in Jira. Change requests are created, updated and edited in Jira. The table updates automatically every time a change is modified there.

Table

Each change in the table contains the following information:

• Title: A brief description of the identified change and a link to the Jira issue identified by its key.
• Status: The status of the change request. Values depend on the configuration of the corresponding Jira issue type, for example Received, Reviewed, Completed and Refused.
• Change Classification: Whether the change request is considered significant or non-significant, according to MDCG 2020-3.
• SW Change: The Software Change classification, following the semantic version: patch, minor or major.
• Assignee: The owner of processing the change request.
• Due Date: The deadline for the completion and release of the change in the affected software items.
• Software Items: The number of software items affected by the change.
• Risks: The number of risks that may affect the change.
• Requirements: The number of requirements related to the change.

Actions

Under the last column on the table you can perform the following actions:

• Link Software Items: click the link icon to link a software item to the change, or to unlink an already associated one. Linked software items are displayed in the drawer under the Traceability tab.

Drawer

Clicking on a row opens a drawer with detailed information about the selected change, in two tabs: Details and Traceability.

To navigate between the linked entities (requirements, risks and software items), select them under the Traceability section in the detailed view.

To go back to previous entities, open the history menu at the top of the detailed view and select the entity of interest.

Details

The Details tab provides, in addition to the information displayed in the table:

• Description: A summary of the change request (current behavior, proposed change, reasons for change, affected components, etc.).
• Priority: The priority level (typically a positive number, where a lower value means a higher priority).
• Affected version: The software component affected by the change.
• Reporter: The user who created the change request on Jira.
• Approval Date: When the change request was approved.
• Acceptance criteria: The criteria to verify and validate that the change was applied successfully.
• Notes: Any additional notes about the change.

Traceability

The Traceability tab shows all the issues linked to the change grouped by:

• Software Items
• Risk Control Measures
• Changes

Click any linked item to see its details.