Sometimes I make changes in JIRA js files. I would like to have a possibility to update the browser cache for all users. I know that they can just to press ctrl + f5. But it’s necessary to avoid any user actions.
If this is your private jira instance you could resolve this by running a proxy server which alters the cache control headers.
However normally Jira is smart enough to fix this issue automatically for you by using cache busting techniques like hashed file names. Or have you disabled those features?
We have our own JIRA server, and I have not disabled cache busting.
The file batch.js is not recreated when some *.js files were modified. Is it possible to forcibly recreate it?
The solution is to change a build number in the pom.xml file, located in jira-core.
1 Like