> 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/creating-your-first-issue.md).
# Creating your first issue
Traditional issues were designed for project managers, not for engineers.
So they're rubbish for tracking issues in your codebase.
Stepsize issues have context baked in, because they're directly linked to your code. Plus, they're visible throughout your software development cycle. **All without leaving your codebase.**
*We know. This is already awesome.*
## **Try it out**
1. **Select** a snippet of code
2. **Use the shortcut `[^/I]`** to create your issue, or right click and select `Create a technical issue`
3. **Add context** to your issue, such as a title, description, and impact
4. Hit `Create issue` to finish creating your issue
Congratulations! You've created a Stepsize issue. You can now see the Stepsize inline annotation indicating that there is an issue attached to this snippet of code.
{% hint style="success" %}
None of your code get uploaded to Stepsize servers. The Stepsize integrations have been designed with privacy in mind. [See our Information Security Guide](https://storage.googleapis.com/stepsize-assets/Stepsize%20Information%20Security.pdf) for more detail.
{% endhint %}
## **What next?**
Let's learn how to convert TODOs into Stepsize issues with a couple of clicks.
It's time to get rid of the great invisible backlog 💪
{% content-ref url="/pages/xRgCTjuiOW71QTNHYFRb" %}
[Adding more code and context to your issues](/stepsize-documentation/issues/adding-more-code-and-context-to-your-issues.md)
{% endcontent-ref %}