Community
Q&A
Confluence
Questions
How do I check the version numbers what am using for Confluence and Jira ?

How do I check the version numbers what am using for Confluence and Jira ?

Instead of publishing an answer just for a simple question with one word answer, dont know why it is making such inconvenience for customer to know the version number of either Jira or Confluence ?

Still am unable to get the answer, earlier versions are very much simple, when i click on the question mark symbol or About Jira on the top of the site, there itself, it was showing the version no, what i installed and using currently, how simple and quick it was.

When content is published, lets make things simple and later you publish the content what ever you want - which would be helpful / not needed for any customer, they take it later on need basis.

3 answers

6 votes

Hello @Chandrasekhar KC

Welcome to the Atlassian community.

What problem are you trying to solve by having a version number for the Cloud applications? If we have a better understanding regarding how not having that information is causing you difficulty perhaps we can better address your concern.

Atlassian has chosen not to apply version numbers to their Cloud applications. I suppose this is because they are constantly deploying small changes and not all instances are updated simultaneously, which would make it incredibly difficult to have a linear version numbering system. There may be small changes for A, B, and C. Customer X's instance may have received only change C so far. Customer Y's instance may have received A & B changes. Customer Z's instance may have received all three changes. How would version numbering work in that scenario?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

3 votes

Hello and Welcome, @Chandrasekhar KC

To build on @Trudy Claspill point, try looking at it from an administrator’s perspective. In the cloud environment, we are dealing with hundreds of changes over time. Traditional versioning does not really fit well with the concept of continuous delivery, where updates are introduced constantly rather than through clearly separated releases. Because of that, Atlassian can easily end up with a certain level of complexity, or even confusion, in how changes and versions are managed and communicated.

That said, I have also heard some positive news: with the latest changes, the bigger updates may become more seasonal and structured, which could make the overall change management approach easier to follow.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

@Arkadiusz Wroblewski I agree, Cloud apps (and marketplace apps for cloud) are a continuous delivery at this point. As updates are mostly pushed, the version number only come to play when splitting hair during troubleshooting.