The only issue tracker
for engineers
In your code editor. Create & see code issues directly in your editor.
Linked to code. See issues affecting the features you’re working on
Integrates with project management tools. Add issues to your sprints, straight from your editor
10x engineers don’t exist,
but 100x codebases do
Get full visibility on ticking time bombs in your codebase.
Diffuse them early, before they explode and derail your projects.
Make issues easy
to spot in the codebase
Code is annotated with related issues, alerting engineers and allowing them to code or investigate with full codebase context.
Make issues easy
to solve
Issues are securely linked to your code, making them much easier to understand, prioritise, and solve.
Goodbye
context switching
Track and browse issues directly in your editor, without ever leaving your workflow.
Features
Link code to issues
straight from your editor
Technical issues require you to see the code to get the full picture.
Make it super easy for your teammates to see the relevant code or even jump to the right spot in the codebase.
See issues in your codebase with annotations
Instantly raise awareness of tech debt across your team.
Ensure bad patterns aren’t repeated and solve issues while you code.
See issues during planning
Easily spot all the tech debt within a specific file or location in your codebase to quickly gauge if your project will require extra work.
Make technical issues visible
The old way
Tech debt issues are hidden in your backlog
The Stepsize way
Tech debt issues are visible in your codebase
"When I plan a sprint, I'm actually able to link tech debt to the new features that we're going to build. We’ve literally been gifted time to work on value-adding features."
Works with your existing tools and workflows
Stepsize works with most code editors and project management tools.
We also support all programming languages.
Code Editors
Project Management Tools
How much is tech debt costing you?
Calculate your costFrequently Asked Questions
What data is leaving my perimeter and going into the Stepsize cloud? What if I’m not allowed to upload anything to the cloud?
None of your code goes into the Stepsize cloud.
The Stepsize integrations have been designed with privacy in mind. We store the minimum amount of 3rd party data needed to provide our service, including code metadata that isn’t sensitive information such as file paths and commit hashes (does not include code).
See our Information Security Guide for more detail.
Why do I need Stepsize when I have Jira?
Tech debt without context, can’t be prioritised.
This creates a vicious cycle in existing backlogs (like Jira).
- Issues are logged
- Issues lack context
- Issues can’t be prioritised
- Backlog becomes overwhelming
- Repeat
Therefore you need Stepsize to decide what to put into Jira.
Stepsize allows you to gain context by allowing engineers to report tech debt straight from their editors. Once you know which debt you want to fix first, it goes into Jira. But until then, you can keep your backlog free of tickets that say “Refactor xyz” with no clear purpose or context.
How will you help us reduce technical debt while we’re under pressure to ship features?
Stepsize is designed to fit into your existing workflow, so engineers can report tech debt without sacrificing roadmap efficiency. Once you have a prioritised list of tech debt, you can start fixing it and actually increase your engineering velocity.
Isn’t there a risk we’ll want to refactor everything even though we don’t need to?
Stepsize has been meticulously designed to focus on context and prioritisation so that you’ll always know which debt is worth your time.
You’ll actually find the opposite — having a clear view of technical debt helps your team focus on impactful work and ignore the rest.
How will Stepsize help us save time and money?
Stepsize increases your team’s velocity by allowing you to fix your most important tech debt.
This means less time wasted on mishandling debt, bugs, downtime, and support requests, which results in happier customers and engineers.
How can we develop this new habit of tracking technical debt?
If you’ve been tracking issues in a spreadsheet or in a backlog, you’ve already been doing it. It’s just an easier process as it all happens in an Engineer’s editor.
Plus, Stepsize displays the data you track in the right places at the right moment, so engineers will be reminded to keep tracking debt.