Sysadmin guide: Usage overview and invalidating browser caches
Living up to its name, our app Project Specific Field Names for Jira is mostly used by project admins. This should make our administration work easier by reducing the number of overall custom fields on your platform. At the same time it should increase customer satisfaction as it allows for a better customization of cutsom fields in the projects.
Usage overview
Navigate to Jira administration > Manage apps > Project Specific Field Names to get an overview of app usage on your platform. The list provides you with links to the project specific field name configurations.
Invalidating browser caches
Project Specific Field Names uses the browser cache to efficiently replace default with custom field names on the supported Jira screens. If a mapping changes, e.g. if the custom field name is edited, the browser will automatically detect that the cached information is no longer valid and will re-cache the mapping.
Just in case something unexpected happens: As a system administrator you also have the possibility to invalidate all cached information for Project Specific Field Names for all of your projects.
Within normal usage it should not be necessary to use the button Invalidate caches now. If the need arises anyway, don’t despair : All it will trigger is for all of your users' browser to freshly load and cache the field mappings defined for the user’s project(s).
If you are interested in how it works in more detail: Open the browser developer console and check the local storage for keys starting with JFIELDS. For Chrome, more information on the local storage is available on https://developer.chrome.com/docs/devtools/storage/localstorage/?utm_source=devtools (external link).