nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Upgrading Jira to latest (5.05) but keep Confluence at 3.5x - is that a good idea?

unknown

Following on from the security advisory the other day, I don't want us to move onto Confluence 4.x because of the withdrawal of wiki markup.

The question is - if we stay on the latest Confl. 3.x, should we just patch Jira 4.x as Atlassian recommend in the advisory? Or can we move on to Jira 5.x without scuppering the relationship between the wiki and Jira?

We use Jira to manage users in both Jira and Confl.

Accepted answers

RianA

Hi Kathleen, there might be incompatibility with Application link. User management wise, it would be okay to stay, but we strongly encourage you to upgrade, cause it will reach its End of Life policy in one year.

All comments

Harry Chan5

Hi, I don't see any loss in functionality happening. Worse case some new functionality that links Confluence and JIRA will simply not work, that's all.

RianA

Nic Brough -Adaptavist-

Mmm, I know why Kathleen isn't looking to upgrade and I mostly agree with her. I think the removal of wiki-markup needs fixing before she'll upgrade. I think you'll need to consider backwards compatibility of Confluence 3.5 and other Atlassian products until that's been addressed.

RianA

Hi Nick, I see, I understand about that concern. But unfortunately so far, there's no plan to put wiki markup back in action according to this. Perhaps you can give it a go with the new editor. I know it's not perfect, but we always welcome feedback

Nic Brough -Adaptavist-

I'm well aware of it. I'm ok with the new editor, but I don't write a lot.

Many of the users are not happy with the replacement. The users here at my main site still won't pass testing on Confluence 4.x. They're happy(ish) with 3.5 and I think Atlassian need to accept that a lot of sites simply aren't going to move to Confluence 4, and hence need to keep later Jira functions compatible with it. If the Jira/Confluence-3.5 integration breaks, that's not going to be a reason to upgrade Confluence, it's going to be a reason to move to another system. At that point, the integration with the Confluence replacement becomes an issue and they start looking at dropping Jira too.

(Apologies to Kathleen, I've rambled off-topic here)

unknown

We were on JIRA 5.0.6 for about 4 months while still on Confluence 2.9.1 I have since upgraded our Confluence instance to the latest and greatest.

During those 4 months all functionality remained the same in terms of JIRA/Confluence linking.

This is a very large unlimited user instance with 2000+ users and we had no tickets during that 4 month period about reduced functionality

We had our detractors with regards to wiki markup as well, but all have come around to the dark side and really enjoy confluence 4.2. So far everyone has been happy with using the wiki markup macro if they really really want to continue to utilize markup.

Hope this helps.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira