A workspace, not an account
Signing up creates an organization. That is not a formality: there is no path into Vorkhurry that produces a user without one, and everything below — projects, roles, issues — hangs off it.
On a plan that needs no payment the workspace exists as soon as you submit the form and you are signed in. On a paid plan nothing is written until the payment provider's signed webhook confirms the payment.
Set up the work
Issue types, statuses, priorities and the transitions between them are your organization's data. The defaults are a starting point; edit them before you have a thousand issues rather than after.
- Create a project and give it a key — that key is what appears in issue ids and in branch names.
- Add the people who work on it as project members.
- Adjust statuses and transitions under Settings → Work if the defaults do not match how you work.
- Create issues, or import them from Jira, Linear or a CSV.
Run the first sprint
The backlog is the ordered queue of everything not yet in a sprint. Rank it, pull work into a sprint, and start it.
Starting a sprint snapshots the commitment. That is what makes the sprint report afterwards mean something — it compares against what was committed, not against what the scope drifted into.