> For the complete documentation index, see [llms.txt](https://docs.released.so/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.released.so/guide/product/changelog/settings/changelog-filter.md).

# Changelog filter

## Configuring the changelog filter

Navigate to **Workspace >** **Settings > Filter** to access the filter settings.

### Jira projects

With the Jira projects setting, you can easily consolidate issues from multiple Jira projects into a unified Release Notes page. This feature provides teams with the flexibility to organize their their work in a project structure that suits them best while effortlessly pulling everything together for a comprehensive release documentation.

To include issues from multiple projects

1. Click the multi-select project dropdown to expand the dropdown list.
2. Review the list of available projects and select the ones that you want to include in your Release Notes.
3. Your selection will be automatically saved.

{% hint style="info" %}
If a project administrator does not have view permission for a previously added project, the project name will be obfuscated.
{% endhint %}

### Version field

Select which version field to use when filtering by version. The field defaults to the standard "Fix versions", but allows you to specify any custom single or multi-version field.


---

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

```
GET https://docs.released.so/guide/product/changelog/settings/changelog-filter.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.