Help center
110 answers about sprints, the board, AI tools and agents, GitHub, and plans. Can't find it? Email contact@orvezo.com.
Owner: everything, including inviting people, billing, GitHub, AI tool access and archiving projects.
Managers: create projects, run sprints, change project settings, add people to projects and create agents.
Members: work on stories in the projects they belong to, and connect their own AI tools.
A blank project starts empty. A template creates the project with starter epics, stories, tags, and a starter sprint so the team has a structured starting point right away. Templates are included in Team and Business, and in the trial.
It means the template creates one sprint with initial sprint-ready work and also creates additional stories outside that sprint. The sprint gives you a starting point for execution, and the backlog holds the rest of the work for later planning.
Yes. Template content is only a starting point. After the project is created, you can edit stories, move them between Parking Lot, Backlog, and Sprint, update epics and tags, and add or remove work as needed.
Export a CSV from that tool. In the project, open Backlog → Actions → Migration import (or the project's Settings → Import). You match the CSV's columns to Orvezo's fields and see a preview before anything is created.
The workspace owner does the import. It is included on every plan.
Claude, ChatGPT, Codex and any other MCP client. They connect to https://mcp.orvezo.com/mcp and you sign in with your own Orvezo account.
Claude (claude.ai or the desktop app): Settings → Connectors → Add custom connector. Paste https://mcp.orvezo.com/mcp, choose Connect, and sign in to Orvezo.
Claude Code: run claude mcp add --transport http orvezo https://mcp.orvezo.com/mcp, then run /mcp and sign in to Orvezo.
In ChatGPT: Settings → Apps & Connectors → Create. Enter https://mcp.orvezo.com/mcp, choose OAuth, and use the client ID orvezo_external_mcp_v1 (no secret). Then sign in to Orvezo.
If there is no Create option, turn on Developer mode first.
Only what you can. It works in your projects, limited to the projects the workspace lets AI tools reach. It can't do anything your role doesn't allow.
The workspace owner turns AI tools on or off, chooses which projects AI tools can reach (all or a list), and chooses who can connect: Everyone in the workspace (the default), Owners and Managers, or Only the owner.
Settings → AI & Agents → Your connected AI tools lists the tools signed in as you, and you can disconnect any of them. The owner sees and can disconnect everyone's.
A named member of the workspace that an AI tool works as, for example "Claude (Ana)". Owners and Managers create agents in Settings → AI & Agents → Add Agent: a name, a description, its sponsors (the people it works for; only they can act as it) and its projects.
Agents never take a paid seat. Free includes 1 agent, Team up to 5, Business unlimited.
Tell your AI tool which agent it is, for example "You are Claude (Ana) in Orvezo". It then names that agent on every change it makes, and each change shows as "Claude (Ana), for Ana" with an Agent badge on cards, comments, notifications, history and the audit log. Several agents can share one AI tool: each change carries the name of the agent that made it. If you have agents and a change doesn't say which one (or "me"), Orvezo refuses it rather than filing it under you.
Yes, like anyone on the team. An agent has an inbox with its assignments, mentions, replies and changes on its stories, and it can read the project's activity.
Create and edit stories; change status, priority, estimates and due dates; assign stories (including to other people's agents); comment, reply and @mention people and agents; add dependencies and tags; create epics; move stories between the backlog and sprints; mark stories blocked; attach files such as screenshots, logs and CSVs; and read attachments, including images.
By default agents can't start, complete, cancel or reopen sprints, delete stories, archive or delete epics or tags, or delete other people's comments and files.
On Business, the owner can turn on "Agents have the same permissions as their sponsor". Even then an agent never has more than its sponsor, and never manages members, billing or settings.
If a sponsor is removed, the agent stops acting for them at once. To stop an agent entirely, archive it in Settings → AI & Agents. Its history stays.
GitHub is included in Team and Business, and in the trial. The workspace owner connects it in Settings → Integrations, which installs the Orvezo GitHub app on the repositories you choose.
No. The GitHub app is read-only. Orvezo reads pull requests to link them to stories and never changes code.
Right after connecting, in Settings → Integrations ("Choose the project this repository is for"), or later in the project's Settings → GitHub. A repository can serve more than one project. If the workspace has only one project, new repositories go to it automatically.
No. Only the workspace owner connects GitHub. Pull requests show their author's GitHub username.
Put the story key in the branch name, the pull request title or its description:
"Fixes POR-12" (also Closes, Resolves, Completes) or just "POR-12": the pull request is the work.
"Part of POR-12" (also Refs, Towards): it is some of the work.
"Skip POR-12": don't link.
In the story's Development section: each pull request with its status (Open, Draft, Merged or Closed), branch, author and how it was linked. Copy branch name gives you a branch name with the key in it. You can also link a pull request by its URL, or Unlink one; an unlinked pull request stays unlinked.
Yes. A commit links to a story when its message contains the story key, for example "WIS-123: fix login". It shows in the story's Development section and as a count on its board card. Commits never change a story's status. To add an older commit, use Link pull request or commit and paste its link or SHA; Unlink removes one.
The Development section appears in projects that use a GitHub repository (project Settings → GitHub). Projects without one don't show it.
Yes, if you turn on "Move stories automatically" in the project's Settings → GitHub. A draft pull request moves the story to In Progress; ready for review moves it to In Review (or In Progress if the project has no review step); merged into the default branch moves it to Done (or In Review, if you choose).
Stories only move forward. A story someone moved back isn't moved again. "Part of" never finishes a story, and another open pull request holds it at review. Each move shows in the story's history as GitHub.
Pull requests that were already open when you connected GitHub appear the next time they change, for example a new commit or an edit to the title. You can also link one now by its URL from the story.
The owner disconnects in Settings → Integrations. This uninstalls the app. Pull requests already on stories stay.
Recent Projects only shows active projects you recently opened. It is not a full project list. To see all projects you have access to, use All Projects or the Jump to project... dropdown. Archived projects don't appear in either; find them under All Projects → Archived.
All Projects shows the projects available to you in the workspace. Recent Projects is just a shortcut list of the projects you visited most recently.
It lets you navigate directly to another project without going back to the project list first. It is a quick-switch control, not a filter.
The owner sees every project. Managers and Members see only the projects they have been added to. Ask an Owner or Manager to add you in that project's Settings → Members.
The owner archives a project in its Settings → General. It moves to the Archived tab on the Projects page and becomes read-only: its stories and history stay, but nobody can change them.
Yes. Open it from All Projects → Archived to view it. To work in it again, the owner restores it from there.
Parking Lot is for work you want to keep but are not planning right now.
Backlog is for active planning and prioritization.
Sprint shows the work in the sprint chosen in the Sprint dropdown on that page: the active sprint by default, otherwise the next planned one.
Either the project has no active or planned sprint (create one on the Sprints page), or the sprint chosen in the Sprint dropdown has no stories yet. Drag stories into it to plan them.
The Board shows the active sprint. A story in the active sprint appears there right away; a story in a planned sprint appears when that sprint starts.
The Sprint panel is driven by the sprint selected in the dropdown. It is not meant to show all sprints at once.
Yes. Sprint planning and sprint execution are not the same thing. A sprint can hold planned work before it becomes the active sprint used on the Board.
A view stores a saved filter setup. The filters below it are the active controls you use to narrow what is shown right now. If your filters differ from the saved view, the page treats that as unsaved changes.
Its status: To Do, In Progress, In Review (if the project uses it) or Done.
An optional step between In Progress and Done, for finished work that someone should check. Owners and Managers turn it on per project in the project's Settings → Workflow ("Add a review step"). Stories can still go straight to Done, and reports count In Review as in progress. Turning it off moves any In Review stories back to In Progress.
The Board always shows the active sprint, while the Backlog sprint panel shows the sprint selected in its dropdown. If you selected a different sprint there, you see different stories.
The Board shows the active sprint, and the header tells you which one and its dates. If no sprint is active, the Board shows the planned sprints instead, and Owners and Managers can start one from there.
The Board shows every story in the active sprint, finished or not. Done stories stay visible until the sprint is completed or they are moved out of it.
Tags, assignee (people and agents), epic, priority, blocked, and dependencies (Ready, Waiting, or Unblocks others). The Backlog has the same filters.
"Depends on" is planned order: this story needs that one done first.
"Blocked by" is an obstacle found during the work: this story is stuck right now because of that one.
Both make a story wait until the other is Done.
Open the story and use its Dependencies section: add a story it waits on, or a story that waits on it, and choose Depends on or Blocked by.
Blocked by (red): stories blocking this one are still open.
Waiting on (amber): stories this one depends on are still open.
Ready (green): everything this story waits on is Done, so it can start.
Unblocks n: n stories are still waiting on this one.
Cards without dependencies show no chips.
It is a To Do order choice: stories that can start (Ready, or with no dependencies) come first, then by priority and key. While it is on, you can't reorder To Do by hand; switch back to Board order to do that.
Orvezo refuses links that would make a circle, for example POR-12 depending on POR-13 while POR-13 already depends on POR-12, directly or through other stories.
On the Dependencies page: in the project, Planning → Dependencies (on a phone, under More). It maps every link between the project's stories.
"Blocked by" links two stories and clears itself when the other story is Done. Marking a story Blocked, with a reason, is for obstacles that aren't a story, such as waiting on a customer. You clear it yourself.
A title, a rich description, where it sits (Parking Lot, Backlog or a sprint), status, priority (Low, Medium, High or Critical), an estimate, a due date, assignees, an epic, tags, and a Blocked flag with a reason. Below it are comments, files, dependencies and its history.
Neither by default: the estimate is a plain number. Use whatever unit your team agrees on.
Yes. A story can be assigned to several people and agents.
Yes. Comments have replies, and you can @mention people and agents. Mentions always notify the person mentioned.
Choose files in the story or in a comment, or paste a screenshot straight in. Each file can be up to 25 MB, on every plan.
Images (PNG, JPG, GIF, WebP) show inline. PDF, text, CSV, Word, Excel, PowerPoint and ZIP files download. Files that could run code, such as SVG, HTML, scripts and programs, are refused.
5 GB on Free, 100 GB on Team and 500 GB on Business, for the whole workspace. The 25 MB limit per file is the same on every plan.
A sprint starts as Planned, becomes Active when it starts, and ends as Completed or Cancelled. A project has at most one active sprint at a time.
Owners and Managers. Members plan and work on stories in sprints but don't change the sprint itself.
Those are the sprint's lifecycle actions, shown to Owners and Managers for the sprint's current state: Start on a planned sprint; Complete Sprint, Reset to Planned and Cancel Sprint on the active one; Reopen on a completed one; Edit on planned and active sprints.
Yes, if no other sprint is active and the previous sprint is completed. Starting early offers to move the start date to today.
Orvezo asks where they go: back to the backlog, or into another planned sprint. They keep their status when they move. Done stories stay in the completed sprint.
It takes the active sprint back to Planned, with its stories still in it, so it can be adjusted before it starts again.
The sprint ends as Cancelled instead of Completed, meaning it was stopped rather than finished. As with completing, Orvezo asks whether unfinished stories go back to the backlog or into another planned sprint.
Planned sprints in a project can't overlap each other; back to back is fine. The next sprint can be planned inside the active sprint's dates, since the active one often finishes early. A sprint can't start before the day the previous sprint was completed.
By dates lets you set the exact start and end dates.
By duration calculates the sprint length based on the duration input rather than manual end-date entry.
Every sprint has its own page: on the Sprints page, click the sprint's name or "View stories and what carried over". It shows what was done in the sprint, what carried over when it closed (and where it went), what was reopened later, and what was moved out during the sprint.
A finished sprint keeps its record. To bring a story back into play, reopen it.
Open the story and choose Reopen…, then pick where it goes (the current sprint or the backlog) and whether it is To Do or In Progress. The finished sprint keeps its history, so velocity and burndown don't change, and the story shows "Reopened from Sprint N". A Done story outside a running sprint can be reopened the same way.
It returns the whole sprint to Planned so it can be started again, if its dates still fit the scheduling rules. Stories that carried over stay where they went. To bring back a single story, reopen the story instead.
A saved view stores a filter setup for the Board, Backlog or My Work, so you can quickly return to it later. Saved views are yours; other people don't see them. They are included in Team and Business.
It means the current filters on the page no longer match the saved view you selected. You are looking at a temporary filter state unless you save it.
It saves the current filter setup as a saved view for that surface and project context, so you can reopen it later without rebuilding the same filters.
Manage views lets you rename or delete existing saved views. It is for maintaining your saved filter presets, not for changing the filters on the page directly.
That chip shows an active filter currently applied to the page. It gives you a quick visual indication of the narrowed state and lets you confirm why only certain stories are being shown.
It removes the active filters currently applied on that page. If you are using a saved view, clearing filters may leave you in an unsaved state until you switch views or save again.
My Work is your personal view across projects, with sections for Assigned to me, Overdue, Due soon, Active sprints, and Needs attention. It is included in Team and Business.
The My Work buckets are based on different conditions. A story can qualify for one bucket without qualifying for another.
That section lists only your assigned stories that sit in an active sprint, matching your filters. It covers all your projects. If none of your assignments are in an active sprint for the scope you selected, the section stays empty.
It lists your assigned stories that are marked blocked, using the same filters as the rest of My Work. If none of your assignments are blocked in the current scope, the section stays empty.
Yes. You can look across all your projects or narrow My Work to one.
The badge shows how many unread in-app notifications you have.
Settings (your avatar, top right) → Account → Notifications. For each event (assigned to me, comments on my stories, replies, sprints starting or ending, due soon, overdue) you choose in-app and email, and whether email comes straight away or in a daily digest. Workspace invitations and @mentions are always on.
In-app and email are set separately for each event, and many events send email in a daily digest by default rather than straight away. Check Settings → Account → Notifications.
Account settings are personal to you: profile, security, and notification preferences.
Workspace settings apply to the whole workspace: General, Members, AI & Agents, Integrations, Plan & Billing, and the Audit log. Owners see all of them; Managers also see the Audit log; Members see General and AI & Agents (their own AI tools and agents). Members, Integrations and Plan & Billing are the owner's.
Each project also has its own settings, opened from the Settings button (gear) at the top right of the project.
Owners and Managers open the Settings button (gear) at the top right of the project. The tabs are General (name, archiving), Members (people and agents in the project), Workflow (the In Review step and an optional definition of done), GitHub (repositories and moving stories automatically) and Import (for the workspace owner).
The settings area uses a settings-specific navigation so account and workspace administration options are easier to access while you are in that section.
Workspace Reports look across all projects. Owners and Managers see them on Team and Business.
A project's Reports cover only that project.
The workspace owner invites people and sets their role and projects in Settings → Members. Owners and Managers change who works in one project in that project's Settings → Members.
Under Account in settings (your avatar, top right → Settings): Profile, Security and Notifications.
Settings → Audit log, on Business. It records who changed what, including changes agents made for their sponsors.
Each export is a CSV file scoped to the page you are on:
Export Backlog exports the backlog
Export Board exports the board
Export Sprint List exports the project's sprints
Export Project List exports the project list
CSV export is included in Team and Business.
Yes. Backlog and Board exports use the filters you have applied, so filter first if you want a narrower file.
Creating manually starts fresh. Import brings in stories from a CSV, such as an export from Jira, Linear, Trello or a spreadsheet.
Free: up to 3 people, 1 agent and 3 projects.
Team: GitHub, My Work, saved views, templates, CSV export, workspace reports, and up to 5 agents.
Business: everything in Team, plus unlimited agents, the audit log, and agents with their sponsor's full permissions.
CSV import is on every plan.
Every new workspace gets 30 days of Business, free, with no credit card. After 30 days the workspace moves to Free unless you choose a plan. Nothing is deleted; features above Free pause until you upgrade.
No. You pay for people only; agents never take a paid seat on any plan. Each plan includes a number of agents: 1 on Free, up to 5 on Team, and unlimited on Business.
Each paid plan has a workspace price that includes the first few people, then a price for each extra person.
Team: $15 a month including 2 people, then $8 a month for each extra person.
Business: $39 a month including 3 people, then $13 a month for each extra person.
For example, a 5-person team on Team pays $15 + 3 × $8 = $39 a month.
Each person who has accepted an invitation and is active in the workspace. Pending invites do not count until they are accepted, and agents never count.
Yearly costs ten times the monthly price, so you get 2 months free. Team is $150 a year including 2 people, then $80 a year for each extra person. Business is $390 a year including 3 people, then $130 a year for each extra person.
Upgrades take effect immediately after the change is confirmed. Charges and credits may be prorated by your billing provider for the remainder of the current billing period.
Downgrades are scheduled for the end of the current billing period. Your current plan remains active until that effective date.
Billing interval changes are scheduled for the end of the current billing period. Your current billing interval remains active until the scheduled change takes effect.
Cancellation is scheduled for period end. Your plan remains active until then. After that, the workspace moves to Free. Nothing is deleted; features above Free pause until you choose a plan again.
Yes. If a cancellation, downgrade, or interval change is scheduled, you can reactivate or remove the scheduled change before it takes effect.
No. Paid places cannot be set lower than the number of active people. To pay for fewer, remove or deactivate people first, then reduce the count.
People beyond those included in your plan are added to your bill straight away, with a prorated charge for the rest of the billing period. Reducing the count also applies straight away and may create a credit on a future invoice.
You can choose a plan during the trial or after it. Free stays active until you upgrade, and paid billing starts after a successful checkout.