How to handle project based versions and backlogs?

[Jibin George]

Hi All,
Need a guidance from your part. Our software has different versions.
We deliver new portals at different time and the versions at the latest time will be the latest one.
So there might be fixes or bugs reported as JIRA tickets coming in old versions as well as new versions.
There might be new features coming in which is handled as tickets.
So what we need is that the older portals which had a previous version should be updated with the related or compatible bug fixes & new features.
Can we manage it in JIRA such that when we select a particular portal detail, we should know or get a list of tickets pending for this portal, so that we will be able to know which all fixes need to be added to this particular portal.
This should happen for the case of different projects having different older versions.

Thanks in advance.

[Walter Buggenhout]

Hi @Jibin George and welcome to the Community!

The built-in feature that you can use in Jira are the versions, which you probably are familiar with.

Jira Software comes with 2 out of the box custom fields that help you manage versions on issues: fix versions and affects versions. The first one helps you indicate the version a ticket was first resolved in. The second one is there to indicate which versions of the product an issue is impacting. When investigating incidents/bugs, it may be key to diagnose all versions of your portal still in use and cautiously listing them all on the tickets to allow you to find out where you still need to deploy fixes.

If you want to take it a step further, you will enter the field of configuration management. Simply put, that would include maintaining an inventory of all active configurations you are managing, where they are living and what e.g. their status, composition, etc. would be. If you need that level of detail, you may want to have a look at Atlassian Assets, which is built into JSM.

Hope this helps!