Changes in JIRA not Visible Until Manual Refresh in Browser
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Actions in JIRA that use popup overlays in the browser such as assigning, resolving, closing, and reopening issues behave strangely and do not visually show the change made. In some cases the action button may appear 'greyed' out. Manually refreshing the page in the browser does appear to show the change. The 'Assign to Me' function may also throw the error "Issue already assigned to <Username>"
Cause
Performance enhancing modules such as mod_pagespeed have been seen to conflict with JIRA's interface and cause strange issues when browsing.
Resolution
Verify if any pagespeed modules are running in the Apache HTTP server by running the following command to list the loaded modules (Linux Only):
# apachectl -t -D DUMP_MODULES
If any pagespeed module is loaded please work with your System Administrator to disable them