Introduce a dedicated Release Version entity, similar to JIRA’s release management, with its own clear lifecycle (create → associate tasks → track progress → mark complete).

Each release should be:

• A first-class object (not just a label or workaround)

• Linkable to tasks so work can be explicitly tagged to a release

• Trackable with status, progress, and ownership

• Automatable (e.g., notify stakeholders when a release is ready, auto-update status when all linked tasks are done)

This would enable teams to plan, track, and ship releases more reliably—without overloading sprints or relying on manual conventions.