|
Napisany przez joitarani99 w Mar 14, 2024 10:16:56 GMT 1
Next is the archive we store all information about applications for at least three years. Based on data for we had service requests faults involving the replacement or repair of equipment requests for maintenance and prevention consulting questions. Thats claims per quarter per month per week an average of claims per day and . per minute. The lions share of them came through the client portal based on Jira Service Desk which we switched to in from HPSM an outdated legacy solution that only works on the desktop and with a problematic update process. Jira has incorporated a lot of processes within the company. All projects are carried out in it engineers are not scattered among services Buy Email List for ordering and sending spare parts and solving requests and clients can monitor all this. And everything would be fine but questions started piling up for Jira too. Its convenient for the company and engineers but not so much for customers. Through Jira Service Desk customers created requests saw their history status and contractor commented on the progress of work and connected new participants in the process. It turned out to be functional but not always convenient. the information content of applications and the correctness of displaying fields but the most pressing problem was the issue of access control. It was this is how chaotic service requests look in Jira Service Desk It was this is how chaotic service requests look in Jira Service Desk The internal Jira portal has a feature all the projects that CROC is managing are visible there. They are available to all customers and this is bad.
|
|