atlassian.com [EasyPrivacy]

[cros13]

The

Code: Select all

-page-analytics.

rule is causing issues with JIRA on Atlassian cloud. Several pages including the Versions page of any JIRA instance fail to load iframes.

An example URL of blocked content:

Code: Select all

https://d1ixbz5qgnvms3.cloudfront.net/example.atlassian.net/s/d41d8cd98f00b204e9800998ecf8427e-CDN/en168s/100008/06bc14165a5685e0b4ab97b9c3e8d147/1000.0.18/_/download/batch/com.atlassian.jira.jira-projects-plugin:release-page-analytics/com.atlassian.jira.jira-projects-plugin:release-page-analytics.js

Would it be possible to get an exclusion rule added for this specific rule for any subdomain of cloudfront.net (which hosts the content) which includes "atlassian.net" in the URL (since the subdomain is different for each project or group)?

I'm not entirely sure how to make a rule that specific.

[intense]

something like this

Code: Select all

@@||cloudfront.net/*.atlassian.net/*-page-analytics$script

[cros13]

Thanks, that works perfectly.

Any chance of getting this added to the EasyPrivacy list?
Getting a lot of bug reports from my JIRA users and the common theme has been that they are using EasyPrivacy with ABP or uBlock.
I've filed a bug report with Atlassian and they are supposed to be changing the URL used for the script but that has an unknown ETA.

[fanboy]

Is there a page where its reproducible?

[cros13]

It impacts only logged in users of a Atlassian Cloud based JIRA bug tracking system.

A lot of open source projects would have open registration. But the easiest to access would be Atlassian's own project for JIRA itself. This page can be accessed with any google account:

Code: Select all

https://jira.atlassian.com/projects/JRA?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page

Or another option is the Releases page for mariaDB (the mysql fork), which allows open registration:

Code: Select all

https://mariadb.atlassian.net/projects/MDEV?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page