Details
-
Story
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Software (SOFTWARE)
-
Sprint# 55 (4 Aug - 17 Aug), Sprint# 56 (23 Aug - 3 Sep)
Description
The EWT API should take the following parameters:
- SkillGroup / Queue Name - Mandatory -
- Conversation ID - Optional
- Task ID - Optional - if specified, the API return the EWT for this queued task. If not specified, the estimated wait time is calculated based on the last task enqueued in the specified queue.
- Priority - Optional - if specified, the EWT for a new task with the given priority is estimated.
Updated MRE API documentation is available from Postman.
Attachments
Issue Links
- tested by
-
CSN-5041 Verify wait time is working fine after restarting mre.
- Open
-
CSN-5042 Verify estimated position is showing with queue id & task id.
- Open
-
CSN-5043 Verify what happens when a task is ended by customer while task is in wait position.
- Open
-
CSN-5044 Verify when a task is in wait position and another agent logs in what happens.
- Open
-
CSN-5045 Calculate the ewt and position of task which is in wait position when an active chat is transferred to other agent.
- Open
-
CSN-5054 Verify ewt and position is shown against queue id and priority number
- Open
-
CSN-5055 Verify ewt through an queue id and empty task id.
- Open
-
CSN-5058 Verify that against an new queue ewt and position is shown.
- Open
-
CSN-5059 Verify that against an empty queue ewt and position is shown
- Open
-
CSN-5060 Verify against a wrong task id EWT is not shown.
- Open
-
CSN-5061 Verify that against a wrong conversation id ewt and position is not shown.
- Open
1.
|
Write test cases of CSN-5022 | Resolved | Umar Ikhlaq |
|
|||||||
2.
|
Test CSN-5022 | Resolved | Umar Ikhlaq |
|
|||||||
3.
|
Estimated Wait Time stops working in case of MRE Failover | Resolved | Umar Ikhlaq |