{"id":34596,"date":"2026-04-28T10:57:30","date_gmt":"2026-04-28T08:57:30","guid":{"rendered":"https:\/\/www.xalt.de\/?p=34596"},"modified":"2026-04-28T10:57:31","modified_gmt":"2026-04-28T08:57:31","slug":"atlassian-aendert-datennutzung-fuer-ki","status":"publish","type":"post","link":"https:\/\/www.xalt.de\/en\/atlassian-aendert-datennutzung-fuer-ki\/","title":{"rendered":"Atlassian changes data contribution for AI from August 17, 2026: What you need to check now as an admin - incl. checklist"},"content":{"rendered":"
\n \"Marcel\n
\n

Author: Marcel W\u00e4nke<\/p>\n

Senior Atlassian AI Consultant at XALT<\/p>\n <\/div>\n<\/div>\n\n\n\n

Atlassian is consistently expanding AI experiences such as Rovo. For AI to really help in everyday life, it needs context - and context comes from patterns in usage. This is precisely why Atlassian is updating its data usage guidelines and introducing new, centralized settings for data contribution.<\/strong> ein.<\/p>\n\n\n\n

Important for you as an Atlassian Admin: This is not a \"sudden siphoning\" of data, but a clearly announced step with advance notice, protective mechanisms, and \u2013 depending on the plan \u2013 configuration options up to an Opt-out<\/strong>. Your task now is to steer the topic toward compliance early on, understand the defaults, and properly prepare your organization for the deadline on August 17, 2026<\/strong>.<\/p>\n\n\n\n

In this article, you will find the classification plus a concrete checklist of what you should do by fall 2026.<\/p>\n\n\n\n

The Atlassian timeline for customizing your settings<\/h2>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n

What you should avoid<\/h2>\n\n\n\n

In practice, the issue rarely fails because of technology - but because of governance and timing:<\/p>\n\n\n\n