Post by account_disabled on Mar 14, 2024 8:32:57 GMT
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 if the problem has become more acute and if something went wrong escalate. It seems like a simple thing but the standard API does not allow you to navigate through a business process from the outside so you had to write your own logic for them. Form to fill out Form to fill out Status of successful escalation of request Status of successful escalation of request The biggest challenge was to make the portal work quickly and responsively.
At first glance this does not seem to be a particularly difficult task but as soon as we changed the logic to a rolebased one differen Buy Email List from standard Jira the pain began. JQL search was also slower than necessary and the Java API for Jira Service Desk was very limited in functionality. I had to do everything from scratch and think about optimizing SQL queries. In addition to achieve the required speed we had to struggle with multithreading. Another interesting thing from a technical point of view is the implementation of translations. Since the functionality of the Java API for Jira Service Desk is limited we had to understand.
For translations in order to get uptodate translations for various fields. In addition we had to tweak Google Guava there in order to cache already found translations and not waste additional time searching for them. However Jira also has advantages as a backend. It is convenient because everything inside is customizable. We managed to make it so that to add a new button or field to the client portal you dont need to go to the front. Everything is configured in Jira and pulled from the project. As a result our managers from different departments can configure the functionality of their sections of the client portal through a familiar interface.
At first glance this does not seem to be a particularly difficult task but as soon as we changed the logic to a rolebased one differen Buy Email List from standard Jira the pain began. JQL search was also slower than necessary and the Java API for Jira Service Desk was very limited in functionality. I had to do everything from scratch and think about optimizing SQL queries. In addition to achieve the required speed we had to struggle with multithreading. Another interesting thing from a technical point of view is the implementation of translations. Since the functionality of the Java API for Jira Service Desk is limited we had to understand.
For translations in order to get uptodate translations for various fields. In addition we had to tweak Google Guava there in order to cache already found translations and not waste additional time searching for them. However Jira also has advantages as a backend. It is convenient because everything inside is customizable. We managed to make it so that to add a new button or field to the client portal you dont need to go to the front. Everything is configured in Jira and pulled from the project. As a result our managers from different departments can configure the functionality of their sections of the client portal through a familiar interface.
