30. Artic Time Efforts

August 2023

40h 30m

https://empyrajira.atlassian.net/browse/AP-2710

Not a bug. Jira 9 had few security updates. According to that the webview will not work and give 405 error until we give a work around. We have given the 405 work around the way we rendered webview has been changed according to the security updates. The issue is fixed.

405 Work around implementation that make the app compatible with Jira 9. And the known rest end points that has been changed in Jira 9 , code structure updating.

September 2023

28h

https://empyrajira.atlassian.net/browse/AP-2744

This is not a bug Invalid credentials and missing folder.

Folder missing and credentials for the platform was invalid in Netx so the files not getting stored instead thrown error. Folder created. And credentials updated. Issue sorted out.

Root cause finding, calls and fixing.
1. Folder wasn't there for new serial numbered images.

2. Credentials issue from the netx instance tat access the image.

October 2023

12h

https://empyrajira.atlassian.net/browse/APP-669

Bug : There was an issue handling the exhibition id some special characters like comma is appended to the id that made the data not getting populated.

Code written to fix the issue.

Code implementation to fix the bug.

April 2024

8h30m

https://empyrajira.atlassian.net/browse/APP-1026

Reason : Jira Server upgrade to DC made many libraries deprecated and made app incompatible.

Solution : Added the new libraries that supports Jira DC. We were able to upload compatible app.

Jira server is upgraded to DC so libraries that supports DC has been replaced.

May 2024

66h

https://empyrajira.atlassian.net/browse/APP-1028

1. Data Missing : For the specific request type Mapping was not there.
   
   Solution : Then Mapping added.
   
   2. API Change : Now in the mapping instead of project ID we got Project Name which is due to the api upgrade by Jira that gives project name instead of id.
   
   Solution : Code implementation rewritten to get the project id from project name in order to make the mapping feature work.
   
   Mapping added then.
   
   The request type is working.

Finding root cause and the New api changes that had prevented the mapping being added with right values. The specific request doesnt have mappings before upgrade. Code updates have been done to support the mappings from new api rest end point. Then mappings added and the solution worked.