Post by joitarani99 on Mar 14, 2024 2:31:22 GMT -7
So that they could immediately fill out a form select the type of incident indicate the priority describe what happened and add participants to the request if necessary. It is quite difficult to customize a boxed Jira Service Desk especially in such a way as to achieve acceptable usability as a result. The labor costs for something beautiful and convenient would be enormous so we decided to write a new frontend from scratch. This was facilitated by our constant practice of developing customer service for which resources are allocated and there is a separate frontend development team specifically for the t internal systems to new processes.
What they wanted to do and how to change it First we prioritized everything and took on only the highest priority items in order to have time to implement an MVP made according to all the rules. We have compiled a table with the Buy Email List functions that we want to transfer to the new portal what to add what bugs to close. The main task was to develop a new more accessible and friendly interface for customers to work with applications. Now displaying the application on the new client portal Now displaying the application on the new client portal.
We needed to preserve the functionality of the old portal plus close the issues mentioned above undesirable availability of all company projects inability to display additional information fields for the client about his application contract serial number or SLA solution description etc.. We did this keeping everything that worked conveniently before. We created a setup that uses the API to access Jira itself and work with the same requests. There is no need to create any additional entities all this is just.
What they wanted to do and how to change it First we prioritized everything and took on only the highest priority items in order to have time to implement an MVP made according to all the rules. We have compiled a table with the Buy Email List functions that we want to transfer to the new portal what to add what bugs to close. The main task was to develop a new more accessible and friendly interface for customers to work with applications. Now displaying the application on the new client portal Now displaying the application on the new client portal.
We needed to preserve the functionality of the old portal plus close the issues mentioned above undesirable availability of all company projects inability to display additional information fields for the client about his application contract serial number or SLA solution description etc.. We did this keeping everything that worked conveniently before. We created a setup that uses the API to access Jira itself and work with the same requests. There is no need to create any additional entities all this is just.