Issue Summary
From Jira version 10.00 and onwards, changing the status of a JSM (Jira Service Management) ticket results in refreshing the whole page and taking longer time to update then in previous versions. Logging work hours and selecting an assignee also creates the same behaviour. This only happens in servicedesk projects.
- the loading issue happens when the JSM issue is accessed from the queue (the URL will have the format /projects/<project-key>/queues/custom/<Portal-ID>/<Issue-Key>)
- the loading issue does not happen when the JSM issue is accessed from the view issue screen (in this case, the URL will have the format /browse/<Issue-Key>)
Steps to Reproduce
- Install Jira version 10.00 and onwards
- Create a Jira ticket in a service desk project
- Make sure to open the ticket in the queue view and not the view issue screen./projects/<project-key>/queues/custom/<Portal-ID>/<Issue-Key>)
- Transition Jira status from any status to another one
- See the whole page refresh taking more Jira performance then it usually did before
- Please see the screen recording:
https://www.transfernow.net/dl/JSDSERVER_16067Recording
Expected Results
The whole Jira page should not refresh
Actual Results
The whole Jira page refreshes.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JSDSERVER-16244 Agents are automatically redirected from a JSM issue to the JSM queue it used to belong to
-
- Gathering Impact
-
- links to
