Are Confluence, Jira, and JSM Cloud becoming more like GUI commercials for premium features?
Perhaps focusing on functional services would be more beneficial, especially regarding all the bugs and illogical behaviors present in those apps!

This situation is quite frustrating!

Note: In addition, the prices are already increasing in October 2024 for standard licence

C'mon, quit with the doublespeak.  This is an ad.  You know it's an ad.  But it's actually worse than an ad; it's a button that doesn't work.  And unless we let ourselves be strong-armed into signing up for your premium services, that's all it will ever be.

The UI doesn't need a button that doesn't work.

Remove it.

P.S.

The best part?  We're paying customers.

Now if we were getting Confluence for free, then sure, OK, ads are always the price of free.

But no, we're paying for Confluence, but apparently we're just not paying enough yet, so Atlassian wants to shove this ad in our faces until we pay more.

It's extraordinary how little respect Atlassian has for its customers.

Organization admins in Premium and Enterprise Plans who have opted out of Atlassian Intelligence will continue see these blank experiences but rest assured, these messages are only visible to Organization admins. 

It would be helpful to hide these distractions for org admins also.   Distractions make using the product harder.

Purely for scientific, experimental and entertainment reasons, I discovered that the following uBlock Origin and AdBlock rules happen to have some interesting effects which may relate to this issue?

Confluence:  This could result in causing the "🌟Define" button (which is in the pop-up while selecting text) to spontaneously disappear (but only when reading, not when editing)

##[data-testid="highlightActionsPopup"] button:has-text(Define)

In fact, I found that this may entirely remove the pop-up when not editing via this broader rule:

##[data-testid="highlightActionsPopup"]

Confluence: Oddly results in removing the pop-up from appearing during editing:

##[data-testid="popup-wrapper"]:has([data-testid="floating-toolbar-items"])

Confluence: Curiously, this causes that "🌟Write" button from the editor toolbar to no longer appear:

##[data-testid="atlassian-intelligence-toolbar-button"]

Jira issues: Has the unusually specific effect of removing the "✨AI" button in the Issues listing (on the far left):

##[data-testid="jql-builder"] li:nth-child(1):has(svg):not(:has(input))

Both organization admins and end users on Free and Standard plans of our Cloud products will continue to see blank experiences for Atlassian Intelligence.

@Danielle Dannenberg Please explain what value this is adding. It has been made very clear that this is not wanted. I am interested to hear the logic behind this decision.

Yes, I was also pleased about this—until Danielle's comment was edited. I'm not quite sure what aspect of fixing this bug just couldn't be done for Free and Standard plans. Or maybe this is the strategy of "if we make it so annoying to use free or standard, maybe we can get you to pay more to upgrade to premium?" 

I will say, this is more than I expected them to do, but I would echo the sentiment that it again feels like the barest minimum fix. Org admins and people who don't pay for every bell and whistle are people too.

So a bit trigger happy to Close the issue?

>  these messages are only visible to Organization admins. 

>  Free and Standard plans of our Cloud products will continue to see blank experiences 

NOT ACCEPTABLE

Hey all - thanks for your patience and feedback. We heard you loud and clear and are able to confirm that blank experiences prompting users to enable Atlassian Intelligence are no longer visible for end users in Premium and Enterprise plans of our Cloud products.

Organization admins in Premium and Enterprise Plans who have opted out of Atlassian Intelligence will continue see these blank experiences but rest assured, these messages are only visible to Organization admins. 

A reminder, organization admins can activate or deactivate Atlassian Intelligence at any time and manage Atlassian Intelligence preferences from Atlassian Administration (Settings > Atlassian Intelligence).

Still evaluating Atlassian Intelligence for your organization? 

• Explore all the Atlassian Intelligence features available to you in Premium and Enterprise Plans, with more features coming soon

• Review Atlassian’s responsible technology principles

• Learn more about how Atlassian is delivering on its data privacy and security commitments
• Get started with Atlassian Intelligence workflows

Both organization admins and end users on Free and Standard plans of our Cloud products will continue to see blank experiences for Atlassian Intelligence. 

This is not a feature but a BUG as implemented. The summarize button in the Chrome browser on Android causes the WHOLE menu bar it's in to "FLOAT" over the page about 1/3 of the way from the top. If you scroll the page, the bar slides with the page still blocking the view. This tells me testing this never occurred on Chrome Android browser clearly. As this point, we are testing moving off Confluence by simply exporting pages as pdfs and republishing to a Web CMS that won't have this issue since Atlassian isn't responding that this is a BUG not a feature request. As others have noted, it SHOULD be configurable by admins by org and / or space.  What we see is Atlassian Product Mgt makes wrong decisions often on how to implement features breaking the value of the product and then waits for users to correct them

https://getsupport.atlassian.com/browse/PCS-269228

I strongly dislike this kind of upselling.

FWIW i just created a Atlassian support request for this, but i was told just to follow and vote this "Feature request"...

I am a large Enteprise user. This is my first login to Jira issues portal.

We have 400+ people. If you had kept it decent, maybe allow snoozing just on a per-user basis for say a month or so – it would have still gotten you and us somewhere, you could have still had conversion numbers and a large enough user base to play with. Not everyone of us is going to opt-out, some of us will try, and everyone would have been open to that.

But you have decided to bully every single one of us, permanently. It's the old school "bad publicity is still publicity" thinking. Thanks to you, my easy answer to everyone in my org who asks about this is – we will in principle not be strong-armed in this way into a feature. Features that require permanent strong-arming to be used are known to be unworthy. You have successfully made your so-called AI feature taboo in our org and established a negative impression, we won't be going anywhere near it now even if you give it for free.

Why annoy paying customers with distracting advertisements that pop-up inline while editing? Guys, it really is so irritating.

Literally 3/4th's of the pop-up  (~300px out of 400px) are repeatedly spamming you for a product that is not enabled and that you don't want.

Shows poor UI/UX consideration for your customers.

I keep clicking on the Summarise button just to confirm that AI really is disabled (huge risk if it isn't). It is distracting and annoying having a disabled "feature" displaying - it makes you doubt if it is really turned off. 

Absolutely ridiculous that you add an annoying marketing message to EVERY LINE I insert on a new page and then say you have no plans to make it optional.  We get it, you have AI !!  Now, let us disable the constant haranguing message "Type /ai for writing assistance".  Thanks for bringing Clippy back, but most people don't want assistance.  If we do, we can remember to type "/ai" without you constantly (constantly, constantly) telling us to.  It makes your product very annoying to use and will drive people to alternatives.

Edit: sorry, this comment might make more sense on https://jira.atlassian.com/browse/AI-3 instead.  The two issues are basically the same.

I'm documenting an internal application in Confluence. I want users to read what I and our internal approvers want them to read. We do not need some AI to randomly give them information that may or may not be correct. Also, we are not going to have a Premium plan, so we can't have this feature anyway. Having a giant button at the top of the page, especially when everything else in the area is an icon, is really begging users to click something that won't get them anything. 

In your screenshots in this story, you show an icon, but on my page it looks like this:

Edit: Didn't realize my screenshot wouldn't display. I see <icon> Summarize on the button.

I agree with the general feeling in the comments here: we do not want prominent noise in our Confluence interface for functionality that is not enabled (and which we have no interest in enabling).

I reported this as a bug and got referred to this issue.

When a disabled feature still has active elements then it’s a bug. The team labeling the removal of the buttons as a “Feature request” is simply incorrect from a customer view.

At least they’re being honest about forcing unwanted in-app ads on paying customers but that doesn’t make it any better business practice.

I hope you’ll reconsider.

At least offer us a button "Do not show this again" or "Hide future advertisements for this product".

ps. ChatGPT is helpful building monkeyscripts to hide them...

Atlassian, y'all say "you hear us"...but then you immediately demonstrate through both word and action that...you don't?

 ...as we are just about to introduce some capabilities that will allow in-context requests and we want to learn from that. In addition, we believe that over time we are assuming a significant amount of the capabilities of our products will be AI powered and we want to ensure we've considered the implications of that and have learnt from customers all their concerns so we can ensure we have addressed them.

...

That being said, we hear you. We will add to our medium-term exploration a way for admins to disable this or hide it so it’s only visible to them. We will also are looking at streamlining the process from end-users buy introducing a way for them to “request” access to AI (so you are aware of the demand), but it not bothering you with lots of notifications. Instead it would batch requests after a period and let you know.

I'll add for myself that:

We will also are looking at streamlining the process from end-users buy introducing a way for them to “request” access to AI (so you are aware of the demand), but it not bothering you with lots of notifications

Sort of says you're explicitly keeping these around because you need end users to badger their admins or else we won't adopt this. I would say right off the bat kind of a crass move, but also....it says a lot about your features if you can't get people to pick up what you're selling unless they're badgered into it.

Just to make absolutely clear there is no way you can say you missed what we are trying to tell you:

There is a significant portion of your customer base that is not interested in AI functionality within these tools. That group will not feel comfortable until they can entirely, completely, and permanently remove this functionality from interacting with any portion of their instance, including advertisements and UI indicators like buttons. Your current proposal of "thinking about disabling this later" and "batching end user requests" does nothing to actually address the problem raised here.

I really don't understand why you keep thinking you understand our needs better than we do....the evidence very clearly points the other way.

In complete agreement with BenM and Huw, here. You've basically put the sweets next to the checkout and left us to deal with the pestering from the kids. The only motivation I can see here is nag-induced profit. 

What worries me most is the phrase: "we believe that over time we are assuming a significant amount of the capabilities of our products will be AI powered". We still don't yet know that models trained on copyrighted material are even legal - there's a movement coalescing that very much says not - and it's unclear whether any liability would fall on the developers or the users. It's giving compliance teams massive headaches all over the world. At the very least I'd expect a little circumspection from product developers looking to offer these capabilities.

We have very good reasons for wanting to turn this off and it would be trivial to implement. What can you possibly hope to 'learn' from a bunch of angry customers that don't want the thing you're developing? (Apart from some interesting new colloquial oaths)

Following on Thomas' comment, a big part of this being a problem is that it puts admins in a difficult position of having to explain in multiple directions why this feature isn't enabled (customers who want it, other IT professionals who may have security concerns, leadership, etc). I think BenM articulated what's concerning about this perfectly, you really ought to take that feedback to heart.  

It bums me out, because in many ways Atlassian is such a great vendor to work with. My customer success rep is great, your support is great, every product engineer I've ever worked with has been fantastic, but whoever is making these decisions really seems to not give a flying rat's patoot about the performance of these tools in a large environment where change needs to be intentional and managed.

Please give us the ability to opt-out of the Atlassian Intelligence feature displaying, this is incredibly disruptive and I am constantly having to explain to leadership that it is actually NOT activated and our data is not being harvested. We are literally paying customers and should not have to be subjected to this experience.

"At this stage we don’t have any immediate plans to disable the discovery of Atlassian Intelligence as we are just about to introduce some capabilities that will allow in-context requests and we want to learn from that." 

What I read from December update is that you will essentially use your users as a test platform. 

That is so wrong in so many ways that I cannot believe. It seems that Atlassian is so brutally ignoring users that it's really annoying.  But nothing lasts forever, we will see how long this can.

hello,

Agree with previous comments about the way Atlassian harasses our end-users with this new feature.

New features should be shared with the admin so that they can be integrated in the portfolio (or not). Our end-users should not be harassed in their daily activities by unwanted information in the UI.

I hope Atlassian will change quickly this approach. 

@Sherif Mansour - Regarding the December 2023 update.

Thanks for the update on this. I appreciate you taking the time to reply. That said, I am still very concerned about Atlassian's approach here and I'm sure I'm not alone. Here is some feedback for your feedback. This is intended to be constructive so apologies if this doesn't come across in text form.

At this stage we don’t have any immediate plans to disable the discovery of Atlassian Intelligence as we are just about to introduce some capabilities that will allow in-context requests and we want to learn from that.

So how about setting up a beta channel or an opt-in testing group instead of forcing this on all customers?

...we want to ensure we've considered the implications of that and have learnt from customers all their concerns so we can ensure we have addressed them.

What do you need to consider the implications for? To avoid disrupting production services? To avoid upsetting clients? To avoid issues around governance and compliance? These are already current issues being experienced due to Atlassian rolling out this feature in the first place, as per this ticket and AI-3. I'm not sure what you're trying to achieve here.

We will add to our medium-term exploration a way for admins to disable this or hide it so it’s only visible to them.

I genuinely cannot understand why this is not already the case. Please ensure that "admin visibility only" is the default option for ALL features moving forward.

We will also are looking at streamlining the process from end-users buy introducing a way for them to “request” access to AI (so you are aware of the demand), but it not bothering you with lots of notifications. Instead it would batch requests after a period and let you know.

This is a solution to a problem that shouldn't exist in the first place. Any "uplift" functionality (including but not limited to AI) should only ever be available for admins to enable when admins determine that it is suitable. Not when a user sees the advertisement (the inexplicably in-app advertisement) for the shiny new toy and asks if they can have it.

.

While I am very disappointed with Atlassian's approach, I appreciate that there is at least some movement in the right direction. I think you will save a lot of unnecessary work and frustration if you apply the approaches suggested in this feedback to the whole product development model (not just this feature and not just Confluence).

LOL and now it appears in our prod Jira as well. Give me strength... 

For those of us who've been around the Atlassian eco-system for a long time your corporate values seem to have fallen by the wayside. 

https://www.atlassian.com/company/values

We for one feel like we've been given a right royal seeing to... 

This aggressive marketing of pushing stuff like this is getting pretty damn old, pretty fast. 

As an enterprise customer who give you millions a year, this behaviour is simply not acceptable. 

There's no way we're going to get AI through our security, compliance and risk departments without a thorough review.

Now we have the AI UI elements all over our production instance of Confluence and we're having to field loads of responses from our users asking why they can't use this. You'll probably do the same with Jira, which will cause us even more problems. 

Do you guys actually use your own tools? Your product owners need a slap. 

Looks like I'm not the first here. The prompts are everywhere and it's incredibly distracting when I'm editing a document. AI-3 gets my vote too, but as a more general principle:

"Dear Atlassian,

Stop advertising at us in your apps. Nobody wants to be reminded constantly about new features they don't want or invited to conferences they don't care about. It's the web-app equivalent of McAfee foistware and it's infuriating.

At the very least, include a 'never show me this again' button.

Sincerely,

Everyone."

Someone has created AI-3 specifically to ask about disabling the /ai prompt in the text editor. Might be worth voting on that one as well.

Again Atlassian BS is to push in your face the stuff that nobody asked for, and then we can vote for what we need.

Since we moved to cloud (and not because we wanted to)  it's only a frustration for us. It cost more, has such a bad administration functionality, all the time Atlassian is trying to upsell, and you have to be careful not to click somewhere and buy something. I will be soon setting up task for people to search for alternative. 

Agree with the suggested solution.

Today our staff is being harassed with messages on Atlassian Intelligence while as an organisation responsible I don't want any AI in the game for the time being - this is a deliberate choice indeed.

We understand and appreciate the developments being made by Atlassian but until further notice we want a clean Confluence without invasive messages.

This refers to my question in the community yesterday (https://community.atlassian.com/t5/Confluence-questions/turn-off-the-ai-suggestion-line-when-editing-a-page/qaq-p/2540711) 

References to Atlassian intelligence also show up in Confluence when highlighting text, as well as on the body of new pages (screenshots attached).

The text on the page disappears when typing but reappears at each new line. This is already ridiculous behaviour for cloud sites that have Atlassian intelligence enabled, so I have no idea why this would show up when the feature is not even enabled.

Please add the ability to disable this feature and ALL references to it.

Edit: unable to add screenshots (getting a permission error).

Since this icon appears to end users even when Atlassian Intelligence is not enabled for the site, it can be confusing to them as to why they cannot use Atlassian Intelligence features. It can also be problematic for admins, who may have to field more questions from end users about why it's not enabled, although it may be a deliberate organizational choice.