DEVREVU · BUILD · PART 1 OF 3 · BEGINNER
Build · Part 1 — Teams & Issues
Start here. Learn how work is organised in DevRev — your team, your workspace, and the issue: the single unit of work everything else is built on. A hands-on beginner path, with Computer, DevRev's AI teammate, alongside you the whole way. No prior DevRev experience needed.
One issue, start to finish
Build is organised team-first: when you open it you land in a team workspace that shows the work that matters to you, not the whole org. Everything your team is building or fixing is captured as an issue — one task, bug, or feature — tracked through its whole life from triage to deployment.
This first part walks the full loop of work capture. You find your team and its views, learn how a team differs from a group and a part, create issues in any of five ways, reuse subtypes and templates to stay consistent, link work into dependencies, then triage and export it — running every action by asking Computer.
The eight sections of Part 1
Section | What you'll do | Why it matters |
|---|---|---|
Get set up on Computer | Open Computer on desktop or web and run your first prompt. | Every section is hands-on — you act by asking your AI teammate. |
Your team workspace | Navigate the team-first layout and the four default views. | You see your team's work, not the whole org. |
Why Teams | Separate a Team from a Group and a Part. | Teams manage work and identity; Groups control access; Parts are the product area. |
Issues explained | Learn the attributes and lifecycle of an issue. | Almost everything in Build revolves around the issue. |
Create issues — five ways | Capture work via form, inline, bulk, draft, or conversation. | DevRev meets you where you work — use whichever is fastest. |
Subtypes & templates | Pick the right subtype, apply a template, tune your record. | Create good issues fast, and stay consistent at speed. |
Links & dependencies | Connect issues with typed links like blocked by. | Make relationships explicit for early warnings on risk. |
Export & triage | Move new issues into backlog, set priority, export to CSV. | Turn a pile of new work into a clear, ordered plan. |
WHAT'S INSIDE
Three foundations you'll build on
Teams & views
Find your way around.
Land in a team workspace, pin your teams, and use the four default views — Issues, Roadmap, Sprints, and Team Health — plus a shared Memory that sharpens Computer's answers for everyone.
The issue
The single unit of work.
Learn every attribute — team, owner, priority, stage, part, subtype — and the three-group lifecycle from Open to In Progress to Closed, with hierarchy and tasks for larger work.
Capture & connect
From creation to triage.
Create issues five ways, reuse subtypes and templates, link blockers and dependencies, then triage and export — the full loop you can repeat every day.
Every issue, at a glance
Attribute | What it means |
|---|---|
Team | Who owns the issue — also sets its ID prefix. |
Owner | The person responsible for resolving it. |
Priority | P0 Urgent · P1 High · P2 Medium · P3 Low. |
Stage | Where it is in its lifecycle — Open, In Progress, or Closed. |
Part | The product area the issue relates to. |
Subtype | The kind of work — Bug, Task, User Story, or Tech Debt. |
Links | Blocked by, parent/child, duplicate, addressed by, dependency. |
Found your team. Captured your work. Now put it in motion in Part 2.
Our customers
Resources
Initiatives
