I'm really tired of JIRA, to the point where I have expressed it publicly: https://www.embeddedrelated.com/showarticle/1772.php
Atlassian enables default data collection to train AI
51–60 of 149 posts
Re: Atlassian enables default data collection to train AI
#52Does this apply to Loom?
Loom isn't mentioned in the Partner materials I have read. That's about all I can say.
Re: Atlassian enables default data collection to train AI
#53The only silver lining I can see in this is that if they replace their existing tooling with AI integration, we might actually get search and confluence that works.
I've lost count of how many times I search for a keyword and get no relevant results, but the document I'm looking for, which contains the keyword, is in my automatic pop-up of recent documents visited.
Re: Atlassian enables default data collection to train AI
#54No surprise here. It's by design.
Re: Atlassian enables default data collection to train AI
#55I really wish I could find a better source to link to for this. By default, all free and paid customers are being opted-in to their data being used for AI training. All your Confluence pages, Jira tickets, etc. https://support.atlassian.com/security-and-access-policies/d... describes how to disable this, but it also appears that the setting to disable this doesn't exist (it's not visible on any of our instances).
Opt-out at the Org level.
To get value out of Rovo, it needs detail. Your over-subscribed Jira power user/admin can't effectively make it happen. No guarantees Atlassian (Rovo itself) can make it happen either, but the patterns are going to develop and evolve closer and closer to the Agents that make the features.
They have a peculiar definition of Metadata, however. It's a proprietary data product derived from user content. It's a bit shit they way they sell it as metadata. It's a derivation. It's a product of Content, so it's Content - privacy safeguards cannot begin to cover the variation.
\"Metadata includes two data types referred to as content attributes and common patterns.
Content attributes are statistical characteristics, numeric fields, and derivatives of your in-app data. Examples of content attributes may include the number of story points assigned to a Jira work item or the complexity of a Confluence page. Common patterns are phrases, keywords, and topics we extract from search queries and results, Rovo Chat (conversations, prompts, and responses), and custom configuration data that are frequently seen across many customers, while omitting rare data that may be unique to your organization. Examples of common patterns may include common words, phrases, or Rovo Chat prompt topics that are frequently used by customers, such as “vacation policy” or “recap team activity.”\"
Re: Atlassian enables default data collection to train AI
#56Does this include repos content in BitBucket?
Re: Atlassian enables default data collection to train AI
#57I really wish I could find a better source to link to for this. By default, all free and paid customers are being opted-in to their data being used for AI training. All your Confluence pages, Jira tickets, etc. https://support.atlassian.com/security-and-access-policies/d... describes how to disable this, but it also appears that the setting to disable this doesn't exist (it's not visible on any of our instances).
That's insane. Every single one of those things is highly sensitive and confidential information. How could you ever trust them after this? That information is priceless for shorting your company on the stock market.
Not that they'd ever do that of course. Nobody with highly sensitive information about rival companies would ever do that.
Re: Atlassian enables default data collection to train AI
#58Omg
Re: Atlassian enables default data collection to train AI
#59Atlassian just goes from misstep to misstep. I still use their products quite often. The amount of P0 bugs I experience is absolutely crazy: - Bitbucket workers are hopelessly out of date (self hosted). We've had to put so many random workarounds in especially for Docker, as they don't keep them up to date enough - I have had a bug in JIRA for years where I can't reorder a new ticket unless I refresh the page - Every…
The search function in Jira has always been unusable. It’s perhaps the worst part of the entire platform, but nice to see they’re still focused on adding features I will never use.
ironically it's the one place where an agent might be of some use and they created one and it's terrible.
Re: Atlassian enables default data collection to train AI
#60Atlassian just goes from misstep to misstep. I still use their products quite often. The amount of P0 bugs I experience is absolutely crazy: - Bitbucket workers are hopelessly out of date (self hosted). We've had to put so many random workarounds in especially for Docker, as they don't keep them up to date enough - I have had a bug in JIRA for years where I can't reorder a new ticket unless I refresh the page - Every…
Jira is buggy as hell these days. Lots of desyncing that forces me to refresh the page. I can have a ticket open on a sprint board and the modal spontaneously closes after a while, forcing me to reopen it frequently. The other week there were tickets that simply refused to show up in their respective sprint board no matter what I did; later the epic magically appeared on the board out of nowhere, then finally the ind…
I'm sure Atlassian's shareholders appreciate your sacrifice.