Summary

Currently, the issue collector delivers a fragment of HTML/JS to embed in the client website that interacts with JIRA via a URL that encodes state in it.

Following on, the client browser will cache the content and a (potentially) outdated resource will be used by the client browser when JIRA or its plugins are upgraded.

This is worsened by the fact that products such as Confluence, Portfolio and Stash are hardcoding these URLs (currently pointing to JAC) in the actual source of these products and are basically using these URLs as "API"

Steps to Reproduce.

1. Create an issue collector in JIRA.
2. Get the html fragment for the issue collector and embed it into a html page.
3. Visit the the html page and use the collector so that the browser caches the content.
4. Make a change to JIRA source such that the content delivered for the URL included in the html fragment provided by the collector is different.
5. Restart JIRA.
6. Visit the external html page and try to use the collector again.

Actual Results

• The content retrieved from the URL by the embedded collector is out of date and does not reflect the changes done in step 4.

Expected Results

• The content retrieved from the URL by the embedded collector is up to date and reflects the changes done in step 4.

Workaround

Clear the browser cache to obtain the new content.