Hey folks, I’m having a bit of trouble with Jira and I’m hoping someone can help me out. We’ve got this issue where bugs appear across multiple versions of our app, and the fixes aren’t rolled out simultaneously for each version. It’s become challenging to determine which version has received a fix, and sometimes our developers miss updating a particular version altogether. I’m looking for a method to view individual statuses for each version directly within the same ticket while maintaining an overall status that updates only when all versions are fixed. I’ve heard that sub-tasks might be a solution, but it could quickly become chaotic without automation. Does anyone know of a plugin that can automatically create sub-tasks for new fix versions?
I’ve been in a similar situation, and we found a solution that worked well for us without relying on plugins or complex automation.
We used a combination of custom fields and a modified workflow. We created a custom field called ‘Version Status’ as a table, with columns for each major version and rows for status (Fixed, In Progress, Not Started). This allowed us to quickly see the status for each version at a glance.
We then modified our workflow to include a ‘Partially Fixed’ status. This let us move tickets to this state when some versions were fixed, but not all. We also added a transition rule that only allowed moving to ‘Resolved’ when all versions in the custom field were marked as ‘Fixed’.
For reporting, we used JQL filters to create dashboards showing which versions still needed fixes across multiple tickets. This approach gave us the visibility we needed without cluttering our board with sub-tasks or relying on external tools.
It took some initial setup, but once in place, it was easy for the team to maintain and provided clear visibility into our version-specific fixes.
I’ve dealt with similar challenges in my projects. One effective solution we implemented was using a combination of custom fields and automation rules. We created a multi-select custom field called ‘Version Status’ with options like ‘Fixed’, ‘In Progress’, and ‘Not Started’ for each version.
Then, we set up an automation rule to update the main ticket’s status only when all versions in the ‘Version Status’ field were marked as ‘Fixed’. This approach allowed us to track individual version statuses without cluttering the main board with sub-tasks.
For visibility, we added a custom ‘Version Status’ column to our board view. This method worked well for us, providing a clear overview without the need for external plugins. It might be worth considering for your setup if you want to avoid the potential complexity of numerous sub-tasks.
maybe try a custom multi-select field for version statuses. we used one called ‘version status’ with choices like fixed and in progress. then we automated the main ticket update when all statuses were fixed. it worked good w/o extra plugins or tons of subtasks.