Versions & milestones
As a project grows, you’ll want to plan not just what gets done but when and in which release. Versions and milestones are two lightweight ways to organize tasks across time, and each has its own dedicated view so you can see the plan take shape.
Versions
Section titled “Versions”A version is a release marker you attach to tasks — v2.1, 2024.10, “Spring Release,” whatever fits how you ship. Tagging tasks with a version groups together everything going out in the same batch, which makes it easy to answer “what’s in the next release?”
Switch to the Versions view to see all tasks grouped by their version. It’s a natural home for release planning: drag work into the version you’re targeting, and watch each release fill up.
Milestones
Section titled “Milestones”A milestone is a named waypoint on your timeline — “Q3 Launch,” “Beta,” “Customer Demo.” Where versions are about what ships together, milestones are about moments you’re working toward. Attach tasks to a milestone to show which push they belong to, then open the Milestones view to see everything lined up against those waypoints.
| Version | Milestone | |
|---|---|---|
| Answers | ”Which release is this in?" | "Which moment are we working toward?” |
| Typical value | v2.1, 2024.10 | ”Q3 Launch”, “Beta” |
| Dedicated view | Versions | Milestones |
A friendly note on “task versions”
Section titled “A friendly note on “task versions””There’s a second, unrelated meaning of “version” worth knowing about, because it quietly protects your work.
Every task carries a small internal version number that increases each time the task changes. When you save an edit, BridgeApp checks that number to make sure nobody changed the task out from under you since you opened it. If a teammate saved first, BridgeApp won’t silently overwrite their change — it’ll ask you to refresh and reapply your edit on top of the latest version.
This is called optimistic locking, and the friendly way to think about it is: BridgeApp has your back so you can’t accidentally erase a colleague’s update. You’ll rarely see it happen, but it’s the reason a whole team can work the same board at once without losing each other’s changes.