> For the complete documentation index, see [llms.txt](https://docs.copia.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copia.io/docs/git-based-source-control/additional-features/issues/milestones.md).

# Milestones

Milestones can be used with Issues to mark important points in the development process, such as the completion of a particular feature or the release of a new version. For example, a problem may need to be addressed, so a Milestone can be created for addressing that problem. Then a user can create an Issue for each step or code change required for that.

Milestones can be accessed under the Issues tab, using the Milestones section.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FEmaNkrUL7lDyAg4lQIKw%2FMilestones1.png?alt=media&amp;token=048ef6bb-d47e-4ee3-9468-3835a3ca9520" alt=""><figcaption></figcaption></figure>

Milestone progress is tracked *(based on the number of Issues or PR's related to the Milestone*). When creating a milestone, you define the name, description and target due date. That is all!

In summary, Milestones are a great project management tool to allow you to group and track work being performed in Issues, to track a set of issues to completion.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.copia.io/docs/git-based-source-control/additional-features/issues/milestones.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.