|
Post by account_disabled on Mar 14, 2024 4:16:47 GMT -5
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 different 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. 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 the structure of the database tables for translations in order to get uptodate translations for various fields. In addition I had to tweak Google Guava there 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.
|
|