> 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/issues/converting-todos-into-issues.md).

# Converting TODOs into issues

Use Stepsize to create better, **more actionable** issues right here in your code editor.

TODOs and FIXMEs lack context and visibility. When you use Stepsize, issues are visible throughout your software development lifecycle. And they're loaded with context, because they're linked directly to code.

## **How to convert a TODO or FIXME into an issue** 🔀

1. **Navigate to `My TODOs`** at the top of the Stepsize sidebar in your code editor
2. In the sidebar, **Select the TODO or FIXME** that you want to convert into an issue

![Create an issue](https://res.cloudinary.com/drvhrxrne/image/upload/v1669985572/samples/product_guides/Screenshot_2022-12-02_at_12.52.42_vyghss.png)

3. **Add context** to your issue, such as a title, description, and impact
4. Hit `Create issue` to finish creating your issue
5. You can now safely delete your TODO. The Stepsize inline annotation indicates 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)

Congratulations! You've created a Stepsize issue from your TODO or FIXME.

![Adding more context](https://res.cloudinary.com/drvhrxrne/image/upload/v1669985668/samples/product_guides/Screenshot_2022-12-02_at_12.54.17_zklipj.png)<br>

## **What next?**

Learn how to resolve issues in Stepsize.

{% content-ref url="/pages/0D0hiBgjP6JpZiBHdcL3" %}
[How to resolve issues](/stepsize-documentation/issues/how-to-resolve-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/issues/converting-todos-into-issues.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.