Relation between components and release versions

Question

In a project we have different components and they can exist in different versions. Eg: component ABC with version 1.0 and 2.0.  When we work on a next version we create a new version under releases.
I would expect that there is a relation in JIRA between the components and the versions, but obvious that is not.  I can create a version of something that is not defined as a component. I would expect by creating a version to have only the choice from components defined in the project.  
Why is there no relation in database between versions and components?

Walter Buggenhout · Accepted Answer

Hi @jeroen_wilmes,

Jira is a flexible system. While you have most likely chosen to use components with a certain way of categorising your work in mind, there are many other ways to do so to support other use cases too.

While I don't know what you decided to use components for, I can give you a very common example where a link between versions and components would be rather ineffective;

All starts with why you create a Jira project in the first place. Suppose you are developing a software application (as a totally random example, e.g. Jira Software). Your product has a database, a web application, mobile apps for Android an iOS, etc. It is quite common to identify those as components in your Jira project. While Jira Software Data Center is currently at version 9.0.x - those components are still the same. So, not having to link / duplicate components when you add a new version has the benefit that you can historically retrieve all issues linked to a single component across multiple versions.

That does not mean you are doing anything wrong in your scenario. Just that you made a different design decision when you got started with your project.

Hope this helps!