> 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.*<br>

## **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

<figure><img src="/files/8cyu66kBhtmEvzXpnEtq" alt=""><figcaption></figcaption></figure>

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.

![Creating your issue](https://res.cloudinary.com/drvhrxrne/image/upload/v1669989064/samples/product_guides/Screenshot_2022-12-02_at_13.50.26_gfk7mm.png)

{% 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 %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://stepsize.gitbook.io/stepsize-documentation/getting-started/creating-your-first-issue.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
