Bug #18867
closedCascade DB -> Perform audit -> 1st audit created in blank is not displayed in Perform audit page.
0%
1) Login as Administrator
2) Click on Actual audit
3) Create a schedule ( 1st audit in blank db) and automatic schedule will be created
4) Login as auditor
5) Click on Perform audit
6) See the action
Description
Perform audit -> 1st audit created in blank is not displayed in Perform audit page.
Files
Updated by Nikhil d over 4 years ago
- Status changed from Open to Resolved
- Assignee changed from Nikhil d to Anonymous
We Created 1st audit for Chad demo and we will not face any issue. Please verify in next build
Updated by Anonymous over 4 years ago
I have verified in previous build after conform in this build, I have raise the issue
Updated by Bijoy P over 4 years ago
- Status changed from TBD to Resolved
- Assignee changed from Bijoy P to Anonymous
Not replicated. Please verify this in next build
Updated by Anonymous over 4 years ago
- Status changed from Resolved to Not Resolved
Still the issue occur
Updated by Anonymous over 4 years ago
- Subject changed from Perform audit -> 1st audit created in blank is not displayed in Perform audit page. to Cascade DB -> Perform audit -> 1st audit created in blank is not displayed in Perform audit page.
Its Replicating. refer audit # 2020-SEP-CEE-CA-5A-MS-1-290
Auditor: keszeyb2 / a1
Updated by Raja S over 4 years ago
Same issue replicate in NXP db also. Refer : CMAS7S1CI-ATMC Fab-GMA-IA-2020-1176
Updated by Nikhil d over 4 years ago
- Status changed from Not Resolved to Resolved
Updated by Anonymous over 4 years ago
- Status changed from Resolved to Fixed with Hotfix
Verified as hotfix
Updated by Anonymous over 4 years ago
- Status changed from Fixed with Hotfix to Not Fixed with Hotfix
Not Resolved in build
Updated by Nikhil d over 4 years ago
- Status changed from Not Fixed with Hotfix to Resolved
inform me at the time if u got issue.. it is not replicating after that( in case it is replicated to you).. how can we fix?
Updated by Anonymous over 4 years ago
- Status changed from Resolved to Yet to Verify
Updated by User Admin over 4 years ago
- Status changed from Yet to Verify to Not Resolved
Updated by User Admin over 4 years ago
- Status changed from Not Resolved to Resolved
Updated by Anonymous over 4 years ago
- Status changed from Resolved to Not Resolved
issue replicate to boopathy
Updated by Nikhil d over 4 years ago
- Status changed from Not Resolved to In Progress
- Assignee changed from Nikhil d to Anonymous
Updated by Anonymous over 4 years ago
- Status changed from In Progress to Fixed in Dev
Discussed with QA need to verify on next build
Updated by Anonymous over 4 years ago
- Status changed from Fixed in Dev to Resolved
Updated by Anonymous over 4 years ago
- Status changed from Resolved to Closed
Verified in Cascade db and blank db