> 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/adding-more-code-and-context-to-your-issues.md).

# Adding more code and context to your issues

Tired of meaningless, contextless issues? Us, too. Stepsize allows you to link multiple code snippets, files or folders to any issue, and add other important info like impact and effort. No more vague issues that aren't directly linked to code. Pretty cool, right?<br>

### **Adding more code** 🧑🏾‍💻

To add more code, navigate to the **RELEVANT CODE** sidebar when setting up your issue. You can either...

* **Add code snippet**: Select any code snippet in a git-tracked file
* **Add file or directory**: Right click on any file or directory and select: `Technical debt > Create an issue`

![Add code to your Stepsize issue](https://res.cloudinary.com/drvhrxrne/image/upload/v1669985680/samples/product_guides/Screenshot_2022-12-02_at_12.54.33_jyjbbw.png)<br>

### **Adding more context**

Adding more context helps you and your team easily find, understand and prioritise issues.

* Add `Labels` to enable your team to find, filter and sort issues. For example, introduce labels like `UX`, `accessibility` or `morale`.
* Add `Impact`. This can integrate with your issue tracker, like Jira or Linear.
* Add `Effort`. This can integrate with your issue tracker, like Jira or Linear.
* Add `Attachments`.

![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?**

One of the best things about Stepsize is you can view issues inline while reading code.

Let's look at how to spot an inline issue annotation.

{% content-ref url="/pages/Cuuxu00xjPYu1JqYMiFM" %}
[How to view inline annotations](/stepsize-documentation/issues/how-to-view-inline-annotations.md)
{% endcontent-ref %}

<br>


---

# 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/adding-more-code-and-context-to-your-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.