@AngelinaIgnatova does that mean you have removed all domains from the blocklist?
Also, please note that 4 weeks is not an acceptable timeline. We can not change our products on a whim, we can’t reimplement an analytics tool in that kind of timeframe. If you don’t believe us, I encourage you to ask your own internal analytics platforms teams what their opinion is on the topic. Atlassian has a 6 month deprecation policy. Restricting previously allowed access is a breaking change and should be operating under said policy.
I agree that the 4 weeks notice period mentioned here wouldn’t give us enough time to switch to another product analytics platform. We have years of analytics data on our tool including dashboards, funnels, segmentation charts and other data that we work with day-to-day. If we would ever switch to another tool, we would need to run it side-by-side with our old tool for a few months so we can still observe long-term trends and gradually move over. It would be a major project for us, consuming many person-months of work.
That won’t be fixed by implementing an allowlist. We can still send arbitrary data, no matter which tool we use, so customers would still have no guarantee if personal data would leak or not. It probably will also not be fixed by implementing an Atlassian-owned solution.
IMHO what would make more sense, is offer customers some kind of log so they can see and verify what we send through the analytics egress. And if they are concerned about data privacy at all, they should just disable the analytics egress for their apps.
There are already too many blockers for this community to move towards Forge. Please don’t add another “long-term solution” that probably won’t make us happy and won’t make customers happy either.
Note that we intent to consult the developer community, such as through a public RFC, regarding potential long-term solutions that will meet our mutual customers’ needs. Once we select a solution, we will add a ticket to the Forge roadmap, ensuring partners are informed well in advance of any upcoming changes.
Your proposal of a log that will help customers understand the data being sent is interesting and will consider it.
I couldn’t find a public RFC for this. When do you plan to have RFC ready?
We have built an extensive analytics ourselves (some AWS lambdas + BigQuery) where we ingest data from different sources to have a holistic view of our customers and their product usage.
It feels like a step in the wrong direction if we lose this holistic view and have to go back to multiple different tools.