Project

General

Profile

Actions

Bug #4650

closed

Gage RR(Attribute) While clicking Save Button system displays "Server Error"

Added by Kiruthika G about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Start date:
02/08/2018
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1. Login MSA module as Module administrator
2. Click on Gage Type
3. Select Type as "Attribute"
4. Create Two different Gage as Attribute Type(A1, A2)
5. Click on Gages
6. Create Gage
7. Click on Gage RR Tab
8. Click on Measurement System Definition
9. Select Type as "Attribute"
10. Click New
11. Enter MS Group(M1), Description and Gage Type as "A1"
12. Click Save
13. Click New
14. Enter the MS Group(M2), Description and Gage Type as "A1"
15. Click on Conduct Gage RR
16. Select the Type as "Attribute"
17. Create one Study (A1)
18. Enter the Mandatory field and Save without calculation
19. Select the Type and complete the study for (A2)
20. Click on Calculate button
21. Click on Save button
22. Observe the Result
23. Click on Show button in listing screen
24. Observe the Result

MODULES:
MSAPRO
Build Cycle:
Cycle 3
Customer:
Issue Dependency:
Dev Commitment to Resolve in::

Description

Gage RR --> When using the same gages for different Measurement System Definition, system displays "Server Error" while saving the data.

Note: Please check this issue in Actions-- GRR


Files

Stability-MSD-Save issue.jpg (114 KB) Stability-MSD-Save issue.jpg Kiruthika G, 02/08/2018 01:14 AM
Actions #1

Updated by Kiruthika G about 7 years ago

  • Description updated (diff)
Actions #2

Updated by Kiruthika G about 7 years ago

  • Steps To Reproduce updated (diff)
Actions #3

Updated by Smitha V about 7 years ago

  • Status changed from New to Open
Actions #4

Updated by Anonymous about 7 years ago

  • Status changed from Open to In Progress
Actions #5

Updated by Anonymous about 7 years ago

  • Status changed from In Progress to Fixed in Dev
Actions #6

Updated by Anonymous about 7 years ago

  • Status changed from Fixed in Dev to Resolved
Actions #7

Updated by Anonymous about 7 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF