NOTE: This guide assumes that you either have Resolvt self-hosted on your server or using resolvt.dev.
Resolvt is an open source tool for managing technical debt. It acts as an issue tracker, allowing developers to create tickets associated with specific code entities, such as functions, methods, and classes. By integrating with source code repositories, Resolvt can track changes to these code entities and calculate the cost of unresolved technical debt. With Resolvt, developers can easily report and track technical debt tickets within their IDE, making it easier to maintain and improve their code.
Some of the benefits of using Resolvt include:
Resolvt supports the Java and Kotlin programming languages and is compatible with IntelliJ IDEA throug Resolvt Integration plugin. It also integrates with GitHub and Bitbucket as source code repository providers.
Before starting using Resolvt you should set up a workspace for your team. To do that:
Note: Unfortunately Resolvt for Bitbucket is not listed in Atlassian Marketplace yet, that’s why you will need to enable development mode for your Bitbucket Cloud workspace to connect Resolvt to it. If it is the case for you Bitbucket will show you a corresponding warning:
![]()
The IDE plugin is required to create technical debt tickets. It also provides the possibility to browse and edit tickets within a project.
Install the Resolvt Integration plugin from the JetBrains Marketplace.
Alternatively, in your IDE go to File > Settings > Plugins > Marketplace tab. Search for “Resolvt” and install the “Resolvt Integration” plugin.
After the plugin is installed, in the IDE:
To invite team members to the workspace:
NOTE: The user you are trying to invite to the workspace must be signed up to Resolvt instance.
When workspace is set up in Resolvt and the pluging is installed to your IDE and connected to Resolvt instance you can report your first technical debt ticket. To do that:
Example above shows that technical debt tickets can be associated with (bound to) specific code entites. You can bind technical debt ticket to an unlimited amount of:
While creating or editing a technical debt ticket in your IDE you can add more then one bindings the same way as it is described above.
Technical debt cost refers to the impact of technical debt on the team performance and code wellbeing.
Resolvt tracks changes to your code and identifies those that occur in code that is bound to technical debt tickets. As a result, the cost is increased when code bound to a technical debt ticket is modified, or when a user upvotes a technical debt ticket. This cost is meant to reflect the additional time, resources, and potential revenue loss associated with maintaining and fixing the problem caused by the technical debt. By tracking the cost, Resolvt can help prioritize technical debt tickets and make decisions on when to address the technical debt.
In some cases the tracking of a technical debt binding can be lost. That, for example, can happen if the method/function or class that was bound to the technical debt ticket was removed.
Bindings which tracking was lost are displayed in the technical debt ticket in a special way:
In some cases, that means the technical debt is no longer applicable (as the code was removed or refactored) and the technical debt ticket can be resolved. You can do it manually using the Edit button in the web UI. Alternatively, you can edit the ticket, removing the binding or creating a new one within the IDE.