Another New Editor complaint! Atlassian owes us an apology!

[Shawn Connelly]

I had come to the Atlassian forum hoping to learn that my untenable difficulties with the new Confluence editor were my error, but now I understand that this edit is truly a ridiculous mess.

Many of my co-workers are running into multiple issues with the new editor, since it became the default editing in the past two weeks. I have instructed them to use the old editor, but now I am very concerned because the old Blank Page icon now says that it's going away soon! When? I have no idea because even the warning was ineptly worded. Doesn't anyone at Atlassian check their work? It says, "In the upcoming weeks, the old editing experience will no longer be available as a..." ... what? If the warning wasn't so wordy, I'd know when it was going away!

Serious! I hope Atlassian is planning to hold off on deprecating the old editor because the new editor is almost unusable! Repeat, UNUSABLE!  

---

Some threads are calling for the product manager involved to be fired. Well, that's pretty severe. LOL

The real blame should be placed on the leaders who decided in the go/no-go decision to launch this inept editor. It would be more than just a single product leader that was involved in that stupid decision.

At the very least, Atlassian should issue a public apology for this gross lapse in judgement, return to the default old editor, and don't dare force a change on their paying customers until they can answer YES these three simple questions:

1. Is the new editor better in all respects?

2. Does the new editor solve a problem or problems?

3. Switching to the new editor will not cause customers any pain, with respect to  compatibility issues with the old editor?

How about it, Atlassian?

[Theinvisibleman · Accepted solution]

Hi there,

I would generally recommend that you first try to upgrade your Confluence first. This is because in my opinion, there is a world of difference between Confluence 2.9.3 and Confluence 5 (and above). There are a lot of new features, and improvements that you might want to check out.

Of course, upgrading your JIRA is also important, but at version 5.1.5, I think your JIRA is rather stable, compared to your Confluence 2.9.3, which is rather unstable and no longer supported.

However, I wouldn't recommend directly upgrading your Confluence to version 5.2.3, as it's currently rather buggy. Also, you probably want to upgrade your Confluence first to version 3.5.x, via the steps mentioned here, and then upgrade it to Confluence 5.1.x via the steps here.

[Sm Tahsin]

Hi Joe,

Many thanks for your recommendations which really counts. We are going to look into upgrade Confluence first.

Now we have few concerns about JIRA 6 in terms of bugs. We are really keen to upgrade our JIRA to JIRA 6. Few features of JIRA 6 in comparison to 5.1.5 will be very beneficial for our organisation. As you agreed that JIRA 5.1.5 is stable at the moment as it has less bugs in it, so can we have same less amount of bugs in JIRA 6? If so then which version shall we choose of JIRA 6?

From the Atlassian's own JIRA, we can see that there are lots work going arround on differents bugs, specially some them are highly related GreenHopper and its worth to mention that we use GreenHopper quite heavily. From the JIRA bug fixing rates by Atlassian and also from the rate of quicker releases of JIRA, we have a feeling that we are not so far from STABLE version of JIRA having less bugs in it. For example, JIRA 6.1 in works and also Atlassian is releasing 6.0.7 tomorrow. So shall wait a bit for that least buggy version?

Apologies, if I am wrong and if we already have that to go for.

Kind Regards,

[Theinvisibleman]

Hi there,

Of course, upgrading your JIRA is also important :)

Seeing as you are keen to upgrade your JIRA to JIRA 6, I would recommend that you upgrade to JIRA 6.0.7, the latest released version of JIRA. There are some new features as well as some fixed bugs, which you can check out here.

Currently, there is no solid release date as to when JIRA 6.1 wil lbe released yet, so you might want to go to 6.0.7 first.

[Sm Tahsin]

Hi Joe,

Thanks again for your reply. It’s true that we are keen to upgrade JIRA due to lucrative features of it but surely we do not want to go for a version where risk of instability is higher than the existing environment. A stable JIRA without the new features of JIRA 6 is always preferable than slightly instable JIRA with full of lucrative features.

We are having approximately 2000 (and growing) users within JIRA-Confluence-Crowd-Greenhopper VM environment and the impact of introducing them into slightly instable environment compared to existing one is definitely not a good practice here like all the other organisations. JIRA is our top priority and it has to up 24/7 and we also made all the BAU communications with all stakeholders and CPs around the world though JIRA and JIRA’s stability also puts a heavy weight on our organisation’s reputation.

I hope, I am able to draw a little scenario where exactly we are now and also seeking your expert and skill opinion about the JIRA upgrade.

Kind Regards,

[Theinvisibleman]

Hi there,

Apologies for the late response.

As far as I know, JIRA 6.0.6 and the latest version 6.0.7 is quite stable. Of course, I understand your concern, seeing as JIRA is highly used by your company.

What I would suggest is that you first perform the upgrade on a test instance/server, and see if everything works fine, and if it suits your requirements. Once adequate checks on the functionalities have been done, then you can proceed with the upgrade of your production instance :)

[Sm Tahsin]

Hi Joe,

Thanks for your response. We are looking forward to have test instance for JIRA 6 and will run a complete test on it.

I do highly appreciate your efforts in this regard.

Best regards

Tahsin

[Theinvisibleman]

Hi Tahsin,

No problem :)

I hope that your test of JIRA 6 proves satisfactory.

Also, please feel free to accept my earlier answer if you are satisfied with it :D

[Sm Tahsin]

Hi Joe,

Many thanks for your recommendations which really counts. We are going to look into upgrade Confluence first.

Now we have few concerns about JIRA 6 in terms of bugs. We are really keen to upgrade our JIRA to JIRA 6. Few features of JIRA 6 in comparison to 5.1.5 will be very beneficial for our organisation. As you agreed that JIRA 5.1.5 is stable at the moment as it has less bugs in it, so can we have same less amount of bugs in JIRA 6? If so then which version shall we choose of JIRA 6?

From the Atlassian's own JIRA, we can see that there are lots work going arround on differents bugs, specially some them are highly related GreenHopper and its worth to mention that we use GreenHopper quite heavily. From the JIRA bug fixing rates by Atlassian and also from the rate of quicker releases of JIRA, we have a feeling that we are not so far from STABLE version of JIRA having less bugs in it. For example, JIRA 6.1 in works and also Atlassian is releasing 6.0.7 tomorrow. So shall wait a bit for that least buggy version?

Apologies, if I am wrong and if we already have that to go for.

Kind Regards,