Enhancements

Enhancements are the unit of product upgrades in DevRev. They represent upgrades to you existing features and capabilities or net new upcoming capabilities or features that decompose into issues for execution. While issues track individual tasks, enhancements represent the "why" and "what" that gives those tasks meaning.

Enhancements make up your roadmap and connect downward to the issues your team works on in sprints - making them the bridge between product strategy and engineering execution.

Attributes

Stages

Enhancements move through a lifecycle that reflects the product development process:

Planning

• Ideation - Early-stage idea, not yet committed.

• Prioritized - Committed for future work.

• Design - Being scoped and designed.

Execution

• In Development - Engineering work underway.

• In Testing - Under validation.

Delivery

• Deployed - Released to production.

• General Availability - Fully available to customers.

Creating enhancements

Navigate to Enhancements from the left nav section of your team and click + Enhancement.

When creating an enhancement:

1. Add a title and description defining the scope.

2. Assign to a Part (the product area being enhanced).

3. Set the owners (typically the product, engineering and design leads).

4. Add all members who will contribute to the work for delivering it

5. Set a target close date.

Dependency management for enhancements

Enhancements support dependency links - both between enhancements and between enhancements and issues. This makes cross-team coordination explicit and queryable.

Link types for enhancements

Visualizing dependencies

Dependencies are visible across views:

• Record view - Linked items show metadata (title, owner, due date, stage) with quick actions to unlink, view, or remind the owner.

• List view - A column shows "Blocked by N items" (highlighted red if any are overdue) and "Blocking N items."

• Board view - Badges on enhancement cards with hover showing the linked items.

• Gantt view - Connector arrows between enhancements indicating dependency direction.

Computer queries for dependencies

• "Show me all enhancements that are blocked."

• "Which enhancements are blocked by the Platform team?"

• "What's blocking the Checkout redesign enhancement?"

For full details on creating and managing links, see Links and dependency management.

Promotion and merging

Promote enhancements

When an enhancement after being delivered becomes a recurring product area, it can be promoted to a Part (feature). Promotion converts the enhancement into a first-class feature / capability/ product in your product hierarchy, inheriting its linked issues, tickets, and customer data.

To promote:

1. Open the enhancement record that is in deployed state.

2. Click Promote action ****available on the banner on top.

3. Choose the parent capability or product the new feature belongs under.

After promotion, the enhancement becomes a feature in Trails. New enhancements can then be created under this feature for future iterations.

Merging enhancements to parent part

When an enhancement represents a meaningful upgrade that has shipped - but isn't large enough to become a net new part on its own - merge it into its parent feature or capability. This rolls the enhancement's delivered value into the existing product hierarchy rather than leaving it as a standalone record.

To merge:

1. Open the enhancement record that is in deployed state.

2. Click Merge action ****available on the banner on top.

Merging consolidates:

• Linked work items and documents transfer to the parent part.

• The enhancement's timeline and comments are preserved for historical reference.

When to promote vs. merge:

• Promote when the enhancement introduces something entirely new that warrants its own place in Trails (a new feature customers will see as distinct).

• Merge when the enhancement improves an existing feature - the value belongs within that feature, not beside it.

Customer feedback loop and impact score

Enhancements in DevRev are not just engineering artifacts - they're directly connected to customer feedback through linked tickets, accounts, and opportunities.

Linking tickets to enhancements

When customer tickets describe feature requests or pain points that an enhancement addresses, link them:

• From the ticket record, use Part attribute to associate it with the right enhancement or create one.

• From the enhancement, view all linked tickets in the Tickets tab.

This creates a closed feedback loop: customers report needs → tickets are linked → enhancement delivers the feature to address it → linked tickets can be notified on delivery.

Customer impact score

The Customer Impact Score quantifies how much an enhancement matters to your customers. It aggregates multiple signals:

• Opportunities - Revenue potential tied to the enhancement (stage and deal size).

• Accounts - Number and strategic importance of affected customers (ARR, tier, active vs. churned).

• Tickets - Volume, severity, and SLA status of linked support requests.

The score is normalized into High, Medium, or Low tiers for quick prioritization. Enhancements with a high impact score affect more customers, more revenue, or more critical SLA-bound tickets.

Use the impact score to:

• Prioritize your roadmap based on real customer demand, not gut feel.

• Give engineers visibility into why their work matters.

• Report to leadership on customer-aligned delivery.

Best practices

Link customer tickets proactively

Establish the ticket→enhancement link as part of your triage workflow. When a support ticket is accepted as a feature request or bug impacting multiple customers, link it immediately. This drives your impact score and ensures customers are notified when the enhancement ships.

Use dependencies for cross-team work

If your enhancement depends on another team's deliverable, add a "Blocked by" link to their enhancement or issue immediately. Don't wait until you're actually blocked - early linking gives upstream teams visibility and lets Computer surface risks in roadmap reviews.

Promote when scope warrants it

If an enhancement keeps spawning follow-on enhancements in the same area, it's a signal that this has become a feature. Promote it to a Part so future work is organized under a proper product hierarchy rather than a growing chain of enhancements.

Merge shipped enhancements into their parent part

Once an enhancement is deployed and validated, merge it back into the parent feature or capability. This keeps your product hierarchy accurate - the feature's customer impact score reflects all the upgrades that have been delivered into it, and your Trails view stays clean rather than accumulating completed enhancements indefinitely.

Learn more

• Computer for Builders course on DevRevU - Roadmap and project planning module covers enhancements and execution tracking.

• Links and dependency management - Full reference for creating and managing dependency links.

• Roadmap - How enhancements surface in roadmap views and planning.

• Parts and Trails - Product hierarchy where promoted enhancements live.