What is the Difference Between Releases and Versions

This #atlassian #jira video will compare releases to versions. Is it the same thing or is it different?

If you like this video, please make sure to give it a thumbs up. If you haven't already, please consider subscribing. If you have any questions about anything discussed so far, please feel free to make sure you leave your question in the comments section.

Audit activities in Jira applications

Jira for Scrum Masters Course:

Jira Fundamentals Course:

Jira Administrators Course

Jira Merch:

Link to my other Atlassian Jira videos

Link to my Atlassian Live Streams:

Link to Atlassian's Jira products:

Link to my Fiverr profile:

Link to my Upwork profile:

Link to my personal website

[hollimessenger]

I'm pumped I now know what fix version means!!

[jsfetzik]

The confusion between the two terms depends on what kind of "products" you work on. I many cases you do not "release" every "version" that is created. This is particularly true for cases where you need to publish or distribute your end result. Which is what a "release" really is.

In the embedded system world that I support we have some legacy products that still need to have new EPROMs installed to do an update. Thus we may have many versions that never get released to customers, because of the hardware and labor costs to distribute it.

[alsothejiraguy]

My theory about why Atlassian calls the object both a version and a release is that they just want to confuse Junior Jira Admins.

[atlasstic]

Atlassian has several logical errors in their products :) I suspect this comes from the confusion of using Jira Software as both a task management tool and a basic management tool through advanced roadmaps. If they had made this correctly then you would have two levels: Version and Release. A Release is what is deployed and made available to the end users and a version is just the tagging of code packages.

[a.h.]

But you can do more organizational stuff with a release.