Project

General

Profile

Actions
Copy link

Feature/Enhancement #26977

open

Edit Risk popup window AP value is not calculated in the flow-up failure severity value, which is calculated by default using only the Direct effect. (Refer Description) NEED MARK'S SUPPORT

Added by Kirubakaran chandran over 1 year ago. Updated 8 days ago.

Status:
Open
Priority:
Medium
Assignee:
Manivannan Uppiliappan
Start date:
12/18/2023
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1. Login as Aqua pro module Administrator
2. Click on the product (Aqua Pro) menu
3. Click on Design VDA and select Failure Analysis
4. Expand the Tree
5. Assign Flow-up failure severity
6. Right-click on Risk (preventive/Detective)
7. Click on Edit
8. Edit Risk pop window will be open
9. Observe the result
10. Go to the DFMEA table (Select Higher context Element)
11. Observe the result

MODULES:
VDA
Build Cycle:
Cycle 0
Customer:
Issue Dependency:
Moved from SP11.3.2 to SP 11.3.2.2
Dev Commitment to Resolve in::

Description

The system displayed an AP value in the Design VDA Edit Risk popup window.
The displayed AP value is not calculated in the flow-up failure severity value, which is calculated by default using only the Direct effect.
EX. DFMEA table (Flow-up failure Severity-2, Occurrance-5, Detection-3) AP value = L
Edit Risk Popup window displayed AP value is H (System calculate Direct Effect Severity-10, Occurrance-5, Detection-3)

Refer TC: http://14.194.186.13:8080/testlink/linkto.php?tprojectPrefix=EwQIMS&item=testcase&id=EwQIMS-27496

Files

Download all files
1. Edit Risk.png (177 KB) 1. Edit Risk.png Kirubakaran chandran, 12/17/2023 03:23 AM
2. DFMEA table.png (152 KB) 2. DFMEA table.png Kirubakaran chandran, 12/17/2023 03:23 AM
Actions
Copy link
 #1

Updated by User Admin over 1 year ago

  • Status changed from New to Open
Actions
Copy link
 #2

Updated by chitra Kalangiam over 1 year ago

  • Assignee changed from chitra Kalangiam to Manivannan Uppiliappan
Actions
Copy link
 #3

Updated by Manivannan Uppiliappan over 1 year ago

AS PER DISUCSSION WITH MANAGER & LEAD, FOR THIS ISSUE WE NEED MARK'S SUPPORT

Actions
Copy link
 #4

Updated by Manivannan Uppiliappan over 1 year ago

  • Subject changed from Edit Risk popup window AP value is not calculated in the flow-up failure severity value, which is calculated by default using only the Direct effect. (Refer Description) to Edit Risk popup window AP value is not calculated in the flow-up failure severity value, which is calculated by default using only the Direct effect. (Refer Description) NEED MARK'S SUPPORT
Actions
Copy link
 #5

Updated by chitra Kalangiam over 1 year ago

While changing the Context Menu AP value is not showing in API. Need Mark's Support

Actions
Copy link
 #6

Updated by User Admin over 1 year ago

  • Status changed from Open to Future Release

status changed as per chitra and team

Actions
Copy link
 #7

Updated by Kirubakaran chandran over 1 year ago

  • Project changed from SP 11.2.0.11 Patches to SP 11.2.0.13 Patches
  • Build Cycle changed from Cycle 1 to Cycle 0
  • Issue Dependency set to SP 11.2.0.11

Moved from SP 11.2.0.11 Patches to SP 11.2.0.13

Actions
Copy link
 #8

Updated by chitra Kalangiam about 1 year ago

  • Tracker changed from Bug to Feature/Enhancement
  • Status changed from Future Release to New
Actions
Copy link
 #9

Updated by User Admin about 1 year ago

  • Status changed from New to Open
Actions
Copy link
 #10

Updated by Kirubakaran chandran about 1 year ago

  • Project changed from SP 11.2.0.13 Patches to SP 11.2.0.14 Patches

Moved from SP 11.2.0.13 Patches to SP 11.2.0.14

Actions
Copy link
 #11

Updated by User Admin about 1 year ago

  • Project changed from SP 11.2.0.14 Patches to SP 11.3.0
Actions
Copy link
 #12

Updated by Kirubakaran chandran 5 months ago

  • Project changed from SP 11.3.0 to SP 11.3.2
  • Issue Dependency changed from SP 11.2.0.11 to SP 11.2.0.11 -> Moved from SP 11.3.0

Moved from SP 11.3.0

Actions
Copy link
 #13

Updated by Shankar Narayanan 8 days ago

  • Project changed from SP 11.3.2 to SP 11.3.2.2 Patches
  • Issue Dependency changed from SP 11.2.0.11 -> Moved from SP 11.3.0 to Moved from SP11.2.0.18 to SP 11.3.2.2
Actions
Copy link
 #14

Updated by Shankar Narayanan 8 days ago

  • Issue Dependency changed from Moved from SP11.2.0.18 to SP 11.3.2.2 to Moved from SP11.3.2 to SP 11.3.2.2
Actions
Copy link

Also available in: Atom PDF