What are ticket versions?
Stop keeping a story buried at the bottom of a feature, or a feature stuck in a never-ending project. Ticket versions let you manage distinct iterations of the same item — clearly separated, easy to track, and fully aligned with your roadmap. Each version has its own timeline, scope, and progress. It’s the end of messy backlogs and zombie tickets 🧟‍♂️.

Why use versions?
📈 Track evolution — Follow how a project, feature, or story progresses over time.
📈 Break it down — Split complex items into clear, deliverable steps.
🧭 Align everyone — Give teams and stakeholders a shared view of what’s coming — and when.

How to create a version?
You can only create a version from within a ticket.
Open a project, feature, or story → click Add version → give it a name and optionally a timeline.
💡 Name versions as you like — v1.0, Sprint 3, Alpha, Beta… whatever fits your flow.

Where to find your versions?
Once created, versions appear automatically in the:
📍 Roadmap
📆 Timeline
📋 Backlog
They’re easy to spot and follow — no more guesswork.

Can I edit a version later?
Yes. You can rename it, change the timeline, or update the list of associated tickets — anytime.