Post by account_disabled on Mar 14, 2024 4:16:50 GMT -5
In order to have time to implement an MVP made according to all the rules. We have compiled a table with the 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 Buy Email List 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 a visually beautiful display of the same requests that engineers are used to working with and for which a business process has already been built. How everything is organized what and how it had to be added. Jira has an open any layers the portal receives data from Jira and vice versa.
It can write it to Jira creating requests or adding comments. However this was not enough to realize all our wishes. As a result we use the basic capabilities of this interface such as registration authorization creating requests and before that we process applications on the backend of the new portal. The backend is written in Java Spring Boot the front end is written using HTML TypeScript Angular. For example on the new portal we have improved the buttons for easy navigation through business processes. With their help the customer can cancel his request evaluate if it has already been resolved or attract attention.
His application contract serial number or SLA solution description etc.. We did this keeping Buy Email List 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 a visually beautiful display of the same requests that engineers are used to working with and for which a business process has already been built. How everything is organized what and how it had to be added. Jira has an open any layers the portal receives data from Jira and vice versa.
It can write it to Jira creating requests or adding comments. However this was not enough to realize all our wishes. As a result we use the basic capabilities of this interface such as registration authorization creating requests and before that we process applications on the backend of the new portal. The backend is written in Java Spring Boot the front end is written using HTML TypeScript Angular. For example on the new portal we have improved the buttons for easy navigation through business processes. With their help the customer can cancel his request evaluate if it has already been resolved or attract attention.