• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Admin - General
    • None
    • 23
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      This ticket tracks the requests to allow enabling/disabling AI by users and groups.

      If you are voting for this, please consider adding the following details:

      1. Name of the organization, your role
      2. Why do you need user/group level control? What impact will you have if these controls aren't provided?
      3. How are you using AI today in the absence of these controls?

            [AI-930] Ability to enable/disable AI for specific users

            Danja Karenko added a comment - - edited

            1. RELEX Solutions, System specialist (de facto interim Atlassian system owner)

            2. Considering the environmental impact of "AI" (and I'd like to emphasize the air quotes around the "intelligence" part), it's borderline criminal to force "AI"-generated search results on users by default, with no option to disrupt or prevent them.

            It prolongs my search process, making for worse UX, because believe it or not: I'm usually able to find what I need in the traditional search results within a few seconds. Loading times were already suboptimal, now they're even worse. As a first- and second-level support agent for Confluence and Jira, I am dealing with complaints from users who are equally impacted and slowed down. "AI" makes us waste working time.

            3. Since "AI" results are not reliable and need to be fact-checked and often corrected, I only use "AI" as a last resort if I can't find/figure something out myself. Every once in a blue moon I have to ask "AI", only to realize it gives me no new information than what I had already figured out the "old-fashioned" way, plus 50% of the time it adds some some gratuitous hallucinations that I need to debunk first before ending up in the same place I already was.

            Danja Karenko added a comment - - edited 1. RELEX Solutions, System specialist (de facto interim Atlassian system owner) 2. Considering the environmental impact of "AI" (and I'd like to emphasize the air quotes around the "intelligence" part), it's borderline criminal to force "AI"-generated search results on users by default, with no option to disrupt or prevent them. It prolongs my search process, making for worse UX, because believe it or not: I'm usually able to find what I need in the traditional search results within a few seconds. Loading times were already suboptimal, now they're even worse. As a first- and second-level support agent for Confluence and Jira, I am dealing with complaints from users who are equally impacted and slowed down. "AI" makes us waste working time. 3. Since "AI" results are not reliable and need to be fact-checked and often corrected, I only use "AI" as a last resort if I can't find/figure something out myself. Every once in a blue moon I have to ask "AI", only to realize it gives me no new information than what I had already figured out the "old-fashioned" way, plus 50% of the time it adds some some gratuitous hallucinations that I need to debunk first before ending up in the same place I already was.
            SET Analytics Bot made changes -
            Support reference count Original: 22 New: 23
            SET Analytics Bot made changes -
            Support reference count Original: 21 New: 22

            1. Org name unnecessary, role is that of a technical director.
            2. I need user-level controls because many users wish to disable this, and the admins won't do it, probably because they have higher priorities and don't have time to learn new ways of disabling new, unrequested obstacles.

            The impact of not being able to disable AI is that the decontextualized, inaccurate, slow, and confusing content slows down me and my team and is, at best, a significant distraction to confluence search. And, the UXD is not.

            1. I am using AI effectively, on an ad hoc basis, because I, like most people, know what I want when I want it.

            Armen Yampolsky added a comment - Org name unnecessary, role is that of a technical director. I need user-level controls because many users wish to disable this, and the admins won't do it, probably because they have higher priorities and don't have time to learn new ways of disabling new, unrequested obstacles. The impact of not being able to disable AI is that the decontextualized, inaccurate, slow, and confusing content slows down me and my team and is, at best, a significant distraction to confluence search. And, the UXD is not. I am using AI effectively, on an ad hoc basis, because I, like most people, know what I want when I want it.
            SET Analytics Bot made changes -
            Support reference count Original: 19 New: 21
            SET Analytics Bot made changes -
            Support reference count Original: 18 New: 19
            Dominique Cardin made changes -
            Remote Link Original: This issue links to "ENT-2574 (Jira)" [ 1015149 ] New: This issue links to "ENT-2574 (Hello Jira)" [ 1015149 ]
            SET Analytics Bot made changes -
            Support reference count Original: 17 New: 18
            Giuliano C. made changes -
            Remote Link New: This issue links to "ENT-2574 (Jira)" [ 1015149 ]

            1. Name of the organization, your role: Org not listing; Executive Officer and Atlassian relationship owner
            2. Why do you need user/group level control? What impact will you have if these controls aren't provided?  AI cannot be enabled for advanced ROVO capabilities without having ability to provide privileges to individuals.  Audit guidelines. AI governance mandates.
            3. How are you using AI today in the absence of these controls?  We cannnot use Atlassian Rovo intelligence capabilities 

            Colton.Kosicek added a comment - Name of the organization, your role: Org not listing; Executive Officer and Atlassian relationship owner Why do you need user/group level control? What impact will you have if these controls aren't provided?  AI cannot be enabled for advanced ROVO capabilities without having ability to provide privileges to individuals.  Audit guidelines. AI governance mandates. How are you using AI today in the absence of these controls?  We cannnot use Atlassian Rovo intelligence capabilities 

              Unassigned Unassigned
              83325d6ab4f4 Monika Gupta
              Votes:
              132 Vote for this issue
              Watchers:
              74 Start watching this issue

                Created:
                Updated: