Low Issue Summary
From Jira version 10.00 and onwards, changing a transition to another status in a Jira 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:
- [^Screen Recording 2025-02-27 at 17.31.39.mov]
Expected Results
The whole Jira page should not refresh
Actual Results
The whole Jira page refreshes
...
Workaround
Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available
Versions Tested
Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below:
| Testing Requirements | Version | Affected Version |
|---|---|---|
| Customers Reported Version | Example: 10.3.3 | Yes |
| Most Recent Bug-Fix Release | 10.4.1 | |
| Previous Major Release | 10.00 | |
| Most Recent LTS | 10.3 | |
| Previous Supported LTS | 9.12 | |
| Other Versions.. | ||
| (Add rows as needed) |
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|