Project

General

Profile

Production Ticket(ST) #11032

SNEKKU - No catalogue can view in memo?

Added by Rashdan Hussin 7 months ago. Updated 6 months ago.

Status:
Ticket Resolved
Priority:
P3 - Medium
Assignee:
Rashdan Hussin
Start date:
22/02/2024
Due date:
28/02/2024
% Done:

100%

Estimated time:
Spent time:
49.00 h
Job Remark:
Ticket Logged Date:
22/02/2024
Ticket No.:
Related Ticket ID:
Type:
Support Request
SLA Initial Response:
22/02/2024
SLA Delivery:
28/02/2024
Esclation Time:
Issue Reoccurance#:
Actual Initial Response:
22/02/2024
Resolution:

1) Try to simulate using MO account to view the catalog using our tablet and got no issue to open and view the catalog.
2) Escalate to level 3. https://app.clickup.com/t/86enqnge5

Root cause: Android version.

Requester ExpectedDeliveryDate:
Delay Justification:
Priority Seq:
Effort (Hour):
External Ticket #:

None

Description

No catalogue can view in memo?

dad098d1-de9e-41db-8971-a08113293a45.jpg (8.29 KB) dad098d1-de9e-41db-8971-a08113293a45.jpg Rashdan Hussin, 22/02/2024 04:53 PM

History

#1 Updated by Rashdan Hussin 7 months ago

  • Status changed from Assigned To to Support In Progress

#2 Updated by Rashdan Hussin 7 months ago

  • Status changed from Support In Progress to Pending Client Feedback

#3 Updated by Rashdan Hussin 7 months ago

  • Status changed from Pending Client Feedback to Support In Progress

#4 Updated by Rashdan Hussin 7 months ago

  • Status changed from Support In Progress to Escalated to Level 3
  • % Done changed from 0 to 80
  • Actual Initial Response set to 22/02/2024
  • Resolution updated (diff)

#6 Updated by Rashdan Hussin 6 months ago

  • % Done changed from 80 to 50
  • Resolution updated (diff)

#7 Updated by Rashdan Hussin 6 months ago

  • Status changed from Escalated to Level 3 to Pending Client Verification

#8 Updated by Rashdan Hussin 6 months ago

  • Status changed from Pending Client Verification to Ticket Resolved
  • % Done changed from 50 to 100

1. This ticket is being closed due to its extended duration at level 3 without resolution.
2. It appears that there has been minimal communication between both side (our side and client side) regarding this issue, which may have contributed to its prolonged status.
3. Our team has conducted thorough troubleshooting, including simulation and replication attempts, in an effort to resolve the issue.
4. It's important to note that this issue seems to be specific to one user, which suggests it may be related to their individual device configuration.
5. Upon investigation, it has become apparent that the problem lies within the user's device itself, an area outside of our expertise for direct support and resolution.
6. Should the issue reoccur or if the user requires further assistance, it is advised to create a new ticket for proper attention and resolution.

We ensure clarity and transparency in our communication regarding the closure of this ticket.

Also available in: Atom PDF