IFRAMES FOR JIRA CLOUD
iFrames for Jira Cloud
Conveniently embed anything you need in Jira Dashboard Gadgets. Atlas Authority created iFrames for Jira Cloud with System and Application Administrators in mind. Now they have a simple gadget that provides them the power to quickly embed external data into their Jira dashboard.
Using iFrames for Jira Cloud
- Add the macro to your dashboard
- Paste the HTTPS link into the URL field
- Adjust your height settings for your dashboard.
Q: Is it just not working?
A: Double check that you’re using a secured link which starts with HTTPS. If your resource isn’t served over HTTPS, it can’t be embedded in iFrames for Jira Cloud.
Q: My gadget is blank. Why?
A: Ad blockers are usually the cause. Try to disable any ad blockers you are currently using.
Q: I disabled my ad blockers, but my gadget is still blank. Why?
A: It is likely that the website requested that it not be embedded. If you or your company owns this site, you can fix this.
Q: How can I fix my website that is preventing my gadget from working?
A: Implement an Access Control Allow Origin HTTP header. If you need additional information, please visit the mozilla docs for a more detailed explanation.
Q: I received an error message that says, "Please set a valid width" AND/ OR "Please set a valid height":
A: This means that you have entered an iFrame size in an invalid format. Please see above for instructions on supported formats.
Q: I received an error message that says, "Please provide a valid URL":
A: This means that you have provided a malformed URL. Please note that we only support URLs with the HTTP and HTTPS schemes.
Q: What are some known issues?
A: If your iFrame comes up as an empty white box it may be one of three things.
1. Try and disable any ad-blockers you are using.
2. Check if Confluence is on HTTPS and the remote site is on HTTP. If this is the case, your web browser is blocking the page. You will need to place the remote site behind HTTPS.
3. If the issue persists, this means that the remote website has explicitly requested that it not be embedded into another site. This could be done using a number of headers including Content-Security-Policy and X-Frame-Options. If you or someone in your organization controls the remote website, you can make some tweaks to fix this. Take a look at the mozilla documentation for a detailed explanation.