> 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/team-and-collaborators/setting-up-stepsize-for-your-team.md).

# Setting up Stepsize for your team

Stepsize transforms the way your team works by linking issues to code. With Stepsize, you get technical issue tracking, collaboration and execution *in your IDE*.<br>

## **How modern engineering teams benefit from using Stepsize**

Creating issues directly in your project management tool (like Jira) interrupts work. At the same time, conversations about issues often lack context.

When you use Stepsize...

1. Engineers track more issues, because issue tracking happens natively in the codebase
2. Engineers are aware of existing issues, because they see issues as inline innotations
3. Issues are much easier to prioritise, because they are innately contextful and directly linked to code.

Engineering teams which adopt Stepsize...

* [x] **Create 10x more issues** 👉 Visibility
* [x] **View 20x more issues** 👉 Awareness
* [x] **Resolve 10x more issues** 👉 Actionability<br>

## **Integrating your project management tool**

Supercharge the project management tools you already use by making it effortless for your engineers to manage issues. All without leaving their editors.

Stepsize integrates with the project management and issue tracking tools you already use, including Jira. You can start a trial to try out our integrations.

**Shallow Jira integration** – Available on our Team Plan. This level of integration will allow you to add issues created with Stepsize into Jira. That issue in Jira is linked to the Stepsize issue.

**Deep Jira integration** – Available on our Business Plan. Issues in Stepsize are automatically created in Jira, and are effectively one and the same. Issue updates of any kind made in one platform are reflected everywhere.

To set up an integration:

1. Open the [Stepsize web app](https://app.stepsize.com)
2. `Integrations` > Select an integration to set up<br>

## **Integrating your version control tool**

Integrating with your version control tool allows you to close feedback loops and surface important information before code gets merged.

Most teams use our GitHub integration. This integration:

* Surfaces issues which relate to code in any pull request
* Surfaces TODOs which need converting into issues
* Allows you to create issues from pull requests

To set up an integration:

1. Open the [Stepsize web app](https://app.stepsize.com)
2. `Integrations` > Select an integration to set up

## **What next?**

Stepsize is a multiplayer tool that's radically more effective for teams than simply using a typical issue tracker.

Invite collaborators to explore Stepsize.


---

# 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/team-and-collaborators/setting-up-stepsize-for-your-team.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.
