Plan
A plan that bends to your team. Not the other way around.
Nest issues as deep as the work needs, and the whole plan stays in sync as you move things around, online or off.
Hierarchy
From the epic to the checklist item — in one tree.
Sub-issues are full issues, never second-class citizens.
Sub-issues share the same status pipeline, assignees, and comments as their parents, so promoting a checklist item to a tracked sub-issue takes one click without losing the thread that got you there.IDs that stick
Every issue gets a short human-readable ID like PLAN-42 that survives renames and re-parenting, so you can paste it into any commit, doc, or chat and it still points home.
Nest as deep as the work demands
Use one level when the project is shallow and six when it gets gnarly, because the shape follows the work instead of a template.
Drill in. Zoom out.
Click an issue to see what it contains, then roll up to a parent for status, time, and progress at a glance, all of it computed live.
Dependencies
See the blockers. Then unblock them.
Cross-project. Not just cross-team.
A frontend issue can block a docs issue can block a launch milestone. New Journey treats them all the same — so nothing slips through the seam between projects.Link the things that link
When one issue is waiting on another, say so across projects or teams, and the whole chain stays visible instead of buried in a comment.
"Ready to start" — automatic
When the last blocker closes, the dependent issue lands on whoever owns it without anyone needing a standup to figure out what is next.
See the whole chain
Click any issue to see what depends on it, all the way down the chain, so the critical path is visible on Monday instead of on Friday afternoon.
Pipelines
Statuses that match how your team actually works.
Built for teams that don't all work the same way.
Every device sees the same history in the same order even after a long stretch with no signal, so the plan you saw at 30,000 feet is the plan you land with.Pick your states
Start with Backlog → In progress → In review → Done, or invent your own pipeline with as many states as your team uses out loud.
Cycles that roll over on their own
Pick a weekly, bi-weekly, or monthly cadence, and unfinished work rolls into the next cycle automatically so Friday afternoon stays clear.
Edit the same thing at the same time
When two people type into the same description on different devices, both edits land cleanly without anyone seeing a pick-a-winner dialog or losing a paragraph.
Time
Log time once. See the truth everywhere.
Log it where the work happened
A small button on every issue lets you log time where the work happened, and the hours roll up to the parent on their own.
Burndown that matches reality
The remaining-work line is computed live from logged time rather than from a spreadsheet someone updates on Friday, so it stays accurate by construction.
Spot the drift before it costs you
See where the team consistently underestimates or overestimates so the next cycle starts with a more honest plan. See it in analytics →
Roadmap
A roadmap that tells the truth — because it can't lie.
One milestone, work from everywhere
A launch milestone can hold frontend, backend, marketing, and docs issues — all from one workspace, all in one view.
Progress is computed, not declared
Milestone progress is the rollup of the work inside it — by count, by estimate, or by hours logged — whichever number your team trusts most.
See it on a timeline
Drag any milestone to reschedule it and hover to see the issues driving its date, because the roadmap is a window into the live plan rather than a slide deck someone forgot to update.
A plan you can hold. Without giving it away.
Bring your team and your data. Keep both. Setup takes minutes — your laptop and your phone do the rest.
FAQ
Frequently asked questions
Can I import from Jira or Linear?
Yes. CSV works today; native Jira and Linear importers ship on the Team plan. Issue keys, hierarchy, comments, and statuses come across — we map your pipeline to ours during import so nothing gets lost.
Are issue descriptions private from the vendor?
Honest answer: chat is, planning isn't yet. Issue titles, descriptions, statuses, and time logs are stored on our servers in a form we can read — that's how on-device search works across the whole workspace today. Chat messages and document comments are sealed end-to-end. We're open about this tradeoff. Full-private planning is on the roadmap.
Do edits work offline?
Yes. Edit on a plane, on a train, in a basement — when you reconnect, your changes merge with anyone else's. No 'pick a winner' dialogs. No paragraphs vanishing.
How do stable IDs like PLAN-42 work without a central server?
Each project tracks its own sequence. IDs come out in order, every device agrees, and two people creating issues offline at the same moment never collide. It's just there when you click — no thought required.