Components versioning

[Davide La Croce]

Hi,

We are a SW team with a single Jira project for backlog/sprint but we are working on many projects that require separate versioning. For now we use the components to classify a certain kind of product for example "apple", "pear", "orange". These fruits are tightly related and and are released together or separately.

I would need to track the pear_v1, apple_v30, orange_v80 with the intent of making a release note that contains the changelog per each component with such version.

We have already explored the possibility of making these components become separate Jira projects with main versioning, this won't work in our team since we need to have a single backlog to track the priorities.

How can I do that?

[Trudy Claspill]

Hello @Davide La Croce 

Welcome to the community.

If you create the projects as Company Managed projects, you could create a Saved Filter that retrieves the issues from all the projects, and then create an Agile board based on that saved filter. The teams could then have one backlog that spans all the projects.