Become a fan of Slashdot on Facebook


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Re:there's so much wrong with what they did... (Score 1) 11

>> On top of that, it breaks other functionality that we depend PDF generation.

Don't even get me started on PDF and word exports... They seem to be breaking things in this area as fast as they fix them.

We are a very small shop in Confluence-universe, and we have been the initiators of multiple bugs in these areas.


Comment Huge thread on Atlassian site, Big lesson (Score 1) 11

There is a problem when a company says "we are the greatest, most customer-focused company" and then does something that even a small % of users feel is strongly anti customer.

Removing a core feature (a defining feature, in fact), of Atlassian's Confluence breaks the implicit customer contract: "We have a feature. Learn to use it. Embed it into your lives, and we, as a software company will take care of you as you invest your time and $ in our product."

This whole issue is completely of Atlassian's making, as they made the choice to yank the feature. They had lots of choices (they could have kept the feature, degraded the feature, deprecated the feature, etc etc) but instead they yanked it and promised there would be no pain.

So we feel pain, and it is a double bad on Atlassian (first the yank, and then the pain, neither of which is expected by a customer).

Then it is a triple bad when Atlassian tries to explain it away "We couldn't handle the round trip problems" (not my problem! so degrade the feature and make round trip go away!) "Everyone loves it" (not relevant.) "We will fix any bug in the RTE" (not relevant, and worse because it has not been true so far.) "The product is moving faster now" (not relevant, not our problem, not necessarily good given the # of regressions I have observed).

Bottom line: We, customers/users, experience pain.

Instead of helping mitigate the pain, or even acknowledging the pain, Atlassian blames us for feeling pain.

Submission + - Atlassian's "Confluence debacle", and the fallout from users ( 11

panzerIVD writes: Disgruntled customers of Confluence (the content-sharing application created by Atlassian) have been sharing their discontent in a somewhat hidden area on the documentation area of Confluence's product page. The negative commnets page have been growing exponentially over the past few months, and especially most recently. So why are customers so dissatistified? One of the major complaints has been Atalssian's decision to remove the text entering option called Wiki Markup Editor in version 4.0. The other complaints range from:
- issues remaining open or inactive for months, if not years.
- the RTE (the Real Time Editor which is the replacement to Wiki Markup Editor) is full of bugs, and is slow to use compared to the WME.
- The connection between Comfluence and Jira is broken.
- Incredulity over the founder's (of Atlassian) abusive use of foul language to describe and justify their decision to remove the Wiki Markup Editor.
(this last one is not a joke,..and is puzzling beyond belief)

Here are some of the complaints from the Confluence doc site:
"You can't have it both ways,.... you can't post sweet sugary positive comments,.....but hide customers that have a legitimate beef with your decision to remove the WME."

"My company just migrated to the version (5.x.x), which took away the wiki markup editor. After experimenting with the new page editor, I am giving up. Editing existing pages and adding is major pain. Inability to see content in its native format is another drawback. In its arrogance Atlassian decided to remove the essential part of wiki functionality, turning Confluence into a non-a-wiki knowledge management product."

"Removing the Wiki Markup Editor from Confluence, like Linux removing the command line interface,...can you imagine the uproar".

"IMO your product managers for Confluence are focused on the wrong priorities. Your reputation is bleeding because of it. Make the new editor support the same editing, search, and revision workflow without serious and unfixable bugs like you currently have, and you'll see this thread quiet down and eventually word of mouth among doc professionals and wiki consultants will improve again."

"I'll add that 15 months ago, in January of 2012, is when I first learned of the 4.x removal of the wiki markup editor. I discovered it when doing routine smoke testing prior to an IT-scheduled upgrade from 3.5.x to the latest version. Naturally, I threw up red flags and prevented our usual upgrade process. We're still on 3.5.x and stopped paying maintenance long ago."

and the most recent:
"It is obvious that Atlassian would rather sanitize the truth and manage perception than simply be who they say they are.
- Still can't get reliable PDF generation out of anything past 3.5.
- Still can't use WYSIWYG editor (which they released, despite their pledge not to, well before it was ready).
Atlassian listens? Fraid not. They're doing for Confluence what Balmer did for Microsoft. And they are damn proud of it.
For the record, I have not heard a single positive response to the change from anyone who has gone through it...except for those that appear on this page. Professional groups, nothing but bad experience... I wonder just how they are collecting their feedback?"

One commenter even went so far as to dutifully list all the issues people have posted in the thread. How many you ask,..well, I count 50 issues.

Matt Hodges, John Masson, and Paul Curren (Atlassian employees) have tried to stem the tide of these negative comments to no avail. They actually seem to make things worse evertime they try to rationalize the removal of the Wiki Markup Editor. There have also been (what appear to be "friends", be they friends, spouses, or actual employees of Atlassian) angry comments fired back at the unhappy users. Seems that all this negative exposure has gotten the better of these supporter's better judgement.

So the question is this,..why would a software company ignore their customer's harsh comments as a result of the removal of functionality?
Coke tried it, Microsoft tried it, and the list goes on,...and after a time,...once the dust settled,...they all buckled and restored the product to its original state. How long will Atlassian stand their ground?

See below for the link to the site where all these complaints can be found. I'm sure the fight is not over yet, if you like Mixed Martial Arts,'re bound to love it. Atalssian's not tapping out,..but they're sure getting a beat down.

Submission + - Microsoft is loosing Backwards Compatibility ( 6

An anonymous reader writes: Microsoft is loosing Backwards Compatibility Religion, breaks printing in Windows 2008. Company admits breaking printing and refuses to fix it.

Slashdot Top Deals

The only perfect science is hind-sight.