> For the complete documentation index, see [llms.txt](https://stepsize.gitbook.io/stepsize-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stepsize.gitbook.io/stepsize-documentation/getting-started/getting-started-with-stepsize.md).

# Getting started with Stepsize

## Welcome to a new way of tracking issues in your codebase 💪

Your code lives in your code editor. Technical issues are about code. So why use traditional trackers like Jira that aren't embedded in your editor and linked to your code !

Stepsize fixes this and brings issue tracking into your code editor.

### **Teams who use Stepsize...**

🚀🚀🚀 

Ship up to **3x faster**

🚀🚀🚀🚀🚀🚀🚀🚀 

Track **8x more** issues than when using trackers like Jira

🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀 

View issues **21x more often** because engineers can see them inline, next to the relevant code

##

## **Who is Stepsize for?**

Stepsize is for teams who want a radically better way of managing technical issues.

You might want to...

* [x] Report more, better issues (without leaving your editor)
* [x] Bring visibility to technical debt
* [x] Create actionable issues, linked to code
* [x] Visualise tech debt in your codebase
* [x] Identify & prioritise tech debt that impacts your product roadmap

##

## **How do I get started?**

Let's start with the basics: [**creating your first issue**.](/stepsize-documentation/getting-started/creating-your-first-issue.md)