...
How to use this page
The release notes on this page have been generated using the Jira issues macro. Each column of the table represents one of the issue fields you selected to include when you created these release notes in Jira.
To edit any of these fields:
Select Edit or type e to edit this Confluence page.
Select the Jira issues macro table and then select the edit icon.
Select Display options to adjust the columns and number of issues that will appear in your table of issues.
Select Insert to save your changes.
...
Improvement on exception handling (MDV-85 / MIBO-386) - when errors are encountered where the error message returned to MIBO system (could be from markertplace API or MIBO code) is empty, server will save the log file and put in the reference code to the log file in the email/conversation back to agent in Zendesk. Example of content - “Reference code: fb8110e109afa". when a similar error occurs and MIBO helpdesk is provided with this reference code, L2 team can then check for the log file to identify what caused the issue.
Improvement when creating outbound message in Mibo Zendesk App (MDV-80 / MIBO-369) - When an agent sends an outbound message, the ticket requester is set as the marketplace user/buyer and the comment poster is set as agent (previously both requester and comment poster is the markletplace user/buyer, this causing confusion to the agent when looking at the ticket). This enhancement require additional logic to call Zendesk API to get the Agent’s zendesk user id.
Enhancement to internal engine (MDV-84) auto restart scheduled task job (job to create new customer record for marketplace user that is newly identified) when the job/task is stuck. ** MDV-84 was deployed as hotfix in the week before 21/3/24
| Info |
|---|
Installation file |
| View file | ||
|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|