Issues

Issues are the primary work items for tracking engineering tasks, bugs, and feature work. They represent what your eam builds - connecting development effort to the product areas that matter, with full lifecycle tracking from triage through deployment.

Issues are attached to parts to align engineering efforts with product priorities. You can add custom attributes to issues to track additional information - see object customization.

Stock Attributes

These attributes can be used in filters and group conditions across various views to track specific work, capacity, and more.

Stages

Issues move through three stage groups:

Open

• Triage - Newly created, needs assessment

• Backlog - Accepted but not yet scheduled

• Prioritized - Ready for upcoming work

In progress

• Development - Actively being worked on

• Review - In code review

• Testing - Under QA validation

• Deployment - Being released

Closed

• Completed - Done

• Won't Fix - Intentionally not addressed

• Duplicate - Consolidated with another issue

Hierarchy and relationships

Issues support parent-child relationships, giving teams flexibility to manage scope and granularity.

• A parent issue can have multiple children, but each issue can have only one parent. Attempting to add a parent to an issue that already has one will fail.

• Issues can be associated with enhancements (larger product improvements) and broken downward intp child issues (smaller units of work). Currently 3 levels of issue hierarchy is supported

• Tasks can be used to track a checklist of small lightweight todos on an issue

In addition to parent-child relationships, issues support dependency links between records. Use Link Records to mark one issue as dependent on another, which is useful for surfacing blockers and sequencing work. See Links and dependency management for details.

Creating issues

Navigate to Work > Issues from the left sidebar and click + Issue, or press C→I from anywhere in the app.

Creation flow

1. Select a team (will be auto selected based on the team view you are on or the most recently selected team)

2. Choose a subtype if applicable - the form adapts to show relevant fields for the selected subtype.

3. Add a title and description.

4. Assign priority and owner.

5. Select the Part (product component).

6. Add tags, link to sprints and fill other non-mandatory fields as relevant

Contextual pre-filling

When you create an issue from a specific context, fields are automatically populated:

• From a sprint board - Sprint and owner are pre-filled.

• From a list view - Active filters (part, owner, priority) carry over.

• From an enhancement record - The parent enhancement is linked automatically.

• From a ticket record via links - Title, description , part are pre-filled from the ticket context

Templates

Access templates directly from the creation modal using the template icon. Templates pre-fill descriptions, fields, and checklists based on your team's configured patterns.

Configure templates at Settings > Templates. See the full Templates documentation.

Smart suggestions

When creating or editing issues, AI-powered suggestions help you:

• Owner, Subtype - ‘Your Regulars’ section suggests most recently used values — so you're always one click away.

• Part - Most recently used values shows up in ‘Your Regulars’ section. Additionally, based on title and description entered ‘Most Relevant’ section shows most fitting part based on semantic match

Inline creation

Create issues without leaving your current view:

• Sprint boards - Click the + button in any column.

• List views - Use the inline row at the bottom of the list.

• Enhancement records - Add issues directly from the Related issues section on enhancement record.

Keyboard shortcuts

Issue subtypes and templates

Subtypes

Subtypes categorize issues by the kind of work they represent. Examples of common subtypes you might create:

• Bug - Something broken that needs fixing.

• Task - A discrete unit of work.

• User Story - New user flow to add to your product .

• Tech Debt - Internal quality and maintenance work.

Admins can create custom subtypes under Settings > Customization > Subtypes. Each subtype can have its own default fields, lifecycle stages, OLA policies, and templates.

Templates

Templates standardize how your team captures work. They pre-fill descriptions, checklists, and field values so creators share the right information every time.

To use a template:

1. Open the issue creation modal.

2. Click the template icon next to the subtype selector.

3. Select a template - the form populates with the template's content.

To manage templates: Go to Settings > Templates. See the full Templates documentation.

Record view personalization

Customize how issue records display for your workflow. Instead of scrolling through 50+ fields to find the 6-8 you regularly use, pin what matters and hide the rest.

Pin and reorder fields

1. Open any issue record.

2. Click the customize icon in the attributes panel.

3. Pin fields - Drag your most-used fields to the top. Pinned fields always display first.

4. Hide fields - Toggle off fields you rarely use. They move to a "Show All" section.

5. Reorder - Drag fields into your preferred sequence.

Your personalization is saved per user and does not affect other team members.

Admins can set org-wide defaults for field visibility under Settings > Object Customization. Individual users personalize on top of those defaults.

Discussion and events

The Discussion tab facilitates communication and collaboration on a given work item across engineers, PMs, designers, and other stakeholders within your organization.

The Events tab provides a log of key events such as owner assignments and changes, stage transitions, and dependency updates.

Best practices

Capture issues from anywhere

Issues don't have to originate from the DevRev UI. Set up capture paths that meet your team where they already work:

• From Computer sessions - Ask Computer to create an issue during any conversation. Say "Create a bug for the login timeout we just discussed" and Computer will draft it with context pre-filled from the chat.

• From Slack - With the Slack integration, click on 3 dots and hit ‘Create Issue’ to turn a thread into a tracked issue. Context from the thread is carried over and is kept in sync with the internal discussions on issue record.

• From DevRev MCP - Use DevRev MCP to create or update issues directly from your favourite coding interface like Claude / Cursor

Automate issue progress with GitHub

Connect GitHub to automatically track development activity against issues:

• Branch creation creates a linked issue automatically (autonomous issues).

• PR opens/merges update the linked issue's stage (e.g., Development → Review → Completed).

• Commit references (mentioning an issue ID in commit messages) create timeline entries on the issue.

This eliminates the "did you update the ticket?" overhead - git activity drives issue state.

GitHub integration documentation

Use templates for consistency

Set up templates for recurring issue types - bug reports, feature tasks, tech debt items. This ensures your team always captures the right context (steps to reproduce, acceptance criteria, customer impact) without relying on memory.

Settings > Templates | Templates documentation

Configure OLAs for engineering accountability

Operational Level Agreements define how quickly your team should acknowledge and resolve issues based on severity, subtype, or part. Use OLAs to:

• Ensure P0 bugs are acknowledged within a defined window.

• Track issue resolution time by team.

• Get alerted before commitments are breached.

OLA documentation

Marketplace snap-ins: OLA Metrics on Issues | Acknowledgment Metric on Issues

Personalize your view

Pin your top 6-8 fields, hide the rest, and arrange them in the order you actually work through them. Your team lead can set smart defaults; you personalize on top.

Keep issues small

If an issue has more than 3-4 child tasks, consider breaking it into multiple issues under an enhancement.

Tag blocked work

Add a "Blocked by" link to the blocking issue so dependencies are visible in sprint health reports and Computer can flag at-risk items proactively.

Learn more

Complete the Computer for Builders learning path on DevRevU for a guided walkthrough covering issues, sprint management, roadmap planning, and analytics.