Hey everyone, I’m struggling with tracking issue statuses across multiple app versions in Jira. We often have bugs that affect several versions, but the fixes don’t always happen at the same time for each one. This makes it tough to keep tabs on which version got the fix and when. I’m wondering if there’s a way to track the status of an issue separately for each affected version, all within the same Jira ticket. Right now, we only have one overall status, which doesn’t update until all versions are fixed. It would be super helpful to see different statuses for each version we’re working on. I’ve heard some people suggest using sub-tasks for each version, but that seems like it could get messy fast. Does anyone know if there’s a plugin or a built-in feature that could help with this? Or maybe you’ve found a clever workaround? Any tips would be really appreciated!
I’ve faced similar challenges in my projects, and here’s what worked for us: we implemented a custom ‘Version Status’ field in Jira. It’s a multi-select field where we can choose the status for each affected version. We defined options like ‘Fixed’, ‘In Progress’, ‘Not Started’ for each version.
To make it more visual, we created a simple dashboard gadget that displays this information in a matrix format - versions on one axis, statuses on the other. This gives a quick overview of the issue across all versions.
For reporting, we use JQL queries to filter issues based on their version-specific statuses. It’s not perfect, but it’s been a game-changer for our team in managing cross-version issues without the clutter of sub-tasks.
One caveat: it requires discipline from the team to keep the statuses updated. We’ve integrated it into our workflow to ensure it stays current.
From my experience, a practical approach is using a custom field for version statuses, coupled with a scripted post-function on your workflow transitions. We set up a multi-select custom field named ‘Version Status’ with options like ‘Open’, ‘In Progress’, ‘Resolved’ for each version.
The scripted post-function updates this field automatically when the main issue status changes. For instance, when moving to ‘In Progress’, it sets all affected versions to ‘In Progress’ in the custom field. This maintains consistency and reduces manual updates.
We also created a custom issue view to display this information prominently. It’s not a perfect solution, but it significantly improved our version-specific tracking without overhauling our entire Jira setup. The key is to automate as much as possible to ensure the data stays current.
have u tried custom fields? u could add a field for each version and update status there. not perfect but might work. another idea is using labels for version-specific statuses, like ‘v1.2-fixed’ or ‘v1.3-in-progress’. easier to filter and search that way. hope this helps!