Production Ticket(ST) #11995
Snekku - hi @Azhar13 jump collection number again CCMC9000018 / 20 CCME5000008 / 10 CCMN5000036 / 38
Job Remark:
Ticket Logged Date:
11/06/2024
Ticket No.:
Related Ticket ID:
Type:
Support Request
SLA Initial Response:
11/06/2024
SLA Delivery:
Esclation Time:
Issue Reoccurance#:
Actual Initial Response:
11/06/2024
Resolution:
1) checked User Database
2) checked mobile databse
3) escalated to technical team for further checking
Requester ExpectedDeliveryDate:
Delay Justification:
Priority Seq:
Effort (Hour):
External Ticket #:
None
History
#1 Updated by Muhammad Arif 3 months ago
- Assignee changed from Muhammed Azhar Mohamed Maideen to Muhammad Arif
#2 Updated by Muhammad Arif 3 months ago
- Due date changed from 13/06/2024 to 18/06/2024
- Status changed from Assigned To to Support In Progress
pending discussion with Jann
#3 Updated by Muhammad Arif 3 months ago
- Assignee changed from Muhammad Arif to Muhammed Azhar Mohamed Maideen
Need to further discuss with Jann as current logic not tally with their expectation.
Current logic for running number will calculate with visit (check in) and non visit outlet(no checkin).
but this caused the running number for visit seems like jump number. the jump number actually is reserve for non visit transaction.
please discuss by today
#4 Updated by Muhammed Azhar Mohamed Maideen 3 months ago
- Status changed from Support In Progress to Escalated to Level 3
- Resolution updated (diff)
#5 Updated by Muhammed Azhar Mohamed Maideen 3 months ago
- Status changed from Escalated to Level 3 to Pending Client Verification
#6 Updated by Muhammed Azhar Mohamed Maideen 3 months ago
- Status changed from Pending Client Verification to Ticket Resolved
- Type set to Support Request
- Actual Initial Response set to 11/06/2024