quality-issue

Derive a Problem Solving process from an issue

After you complete creating an issue, you can specify that the issue is the source of a Problem Solving process by deriving a Problem Solving process from the issue. This links the source issue to the implementing Problem Solving process.

You can view the link between the issue and the Problem Solving process because the source issue is added to the Related Issues and Problem Solvings section in the Overview tab of the Problem Solving process.

After deriving a Problem Solving process, in the Overview tab of the issue, the derived Problem Solving process is displayed in the Implemented by section.

The following video shows how to derive a Problem Solving process from an issue.

Procedure

From Launcher, click Changes .

If this option is unavailable, search for it. You can pin it from the search results for future access.

From the CHANGES folder, select and open the issue that you want to use as the source of the Problem Solving process.
Choose More Commands

New

Derive Change.

To derive a Problem Solving process for a specific symptom defect, in the Symptom Description tab, select the defect, and click Derive Problem Solving Process . Note When you do this, the symptom defect is automatically added to the Defect section.

In the Derive Change panel, select Problem Solving.
In the Synopsis box, summarize the Problem Solving process.
In the Description box, describe the Problem Solving process.
From the Category list, select the appropriate category.
From the Sub-Category list, select the appropriate subcategory.
Specify a proposed due date.

Some companies use a standard operating procedure where an issue must be completed within a specific duration. This duration is based on the Priority of the issue. If your company has defined this standard operating procedure for you, you must specify a Proposed Due Date that matches the priority of the issue. For example, if the Priority is High, set the Proposed Due Date to 30 days and earlier from the Creation Date of the issue. Depending on the Priority of the issue, set the Proposed Due Date as follows:

Priority

Duration assigned to Proposed Due Date

High

Proposed Due Date must be set to 30 days and earlier from the Creation Date

Medium

Proposed Due Date must be set to 45 days and earlier from the Creation Date

Low

Proposed Due Date must be set to 60 days and earlier from the Creation Date

Your administrator can configure the duration assigned to the Proposed Due Date as per the business requirements. If the Proposed Due Date is not automatically set to a duration based on the assigned Priority, the administrator has disabled this option for your company. Note The Proposed Due Date of the issue must not be later than the Due Date of the assigned quality actions.

To assign a workflow to the issue, select the required workflow from the Workflow list. By default, the Quality Issue Process workflow is assigned to the issue. You can choose to use this workflow, assign a different workflow, or remove a workflow from the issue.
(Optional) To add a symptom defect to the Problem Solving process being derived, do the following:

In the Defect section, click Add Defect.

To specify how the issue's symptom defect is used as the problem description defect in the Problem Solving process, select one of the following:

Select Carryover to link and use the issue's symptom defect as the problem description defect in the Problem Solving process. If you edit the defect in the Problem Solving process, the updates are reflected in the issue's symptom defect as well.

Select Duplicate to create a copy of the issue's symptom defect as the problem description defect in the Problem Solving process. If you edit the defect in the Problem Solving process, the updates are not reflected in the issue's symptom defect.

The symptom defect's failures, attachments, and quality actions are transferred to the Problem Solving process. Note You can add only one symptom defect at a time. If you have selected a symptom defect, and clicked Derive Problem Solving Process , then the selected symptom defect is automatically added to the Defect section.

In the Add Defect panel, select the required symptom defect, and click Add.

Note This panel displays only those symptom defects that are not already used as a source of a Problem Solving process. You can derive a Problem Solving process from a symptom defect only once. After you complete the derivation, the symptom defect is no longer available for derivation.

Do one of the following:

To continue editing later, click Derive. The Problem Solving process is derived and displayed in edit mode. You can send it for resolution later.

To send it for resolution immediately, click Derive and Submit. The Problem Solving process is derived and displayed in edit mode.

Note You can also derive an engineering change request (ECR), engineering change notice (ECN), or Simple Change from an issue.