# Filter

<figure><img src="/files/2Eepw3BbLu5mWCqh6NK3" alt=""><figcaption><p>ssue filter in the staging area</p></figcaption></figure>

The panel on the right hand side of the post editing view is called the staging area.

The staging area makes it a breeze to review issues before they get added to the announcement. Issues are sorted by type, so you can easily spot new features, minor improvements, and bug fixes.

## Changelog filter settings

The changelog filter settings form the foundation of the filter that determines which issues to include in your changelog.

Access the filter settings in your workspace under **⚙ Settings > Filter**.

### Jira projects

Your Jira project settings define which issues are included in your changelog. You can choose a single project or include issues from multiple projects in your updates.

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="warning" %}
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.

## Filter

Using the filter in a post allows you to narrow down the list of Jira work items to include in your post. The basic filter provides the following filter options

### Basic Mode

<table><thead><tr><th width="260.5">Filter</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td><strong>Done since</strong></td><td>Include issues moved into the done status category since a specific date. This filter uses the <code>statusCategoryChangedDate</code> to determine the date.</td><td></td></tr><tr><td><strong>Version</strong></td><td>Include issues with a specific version.</td><td></td></tr><tr><td><strong>Label</strong></td><td>Include issues with a specific label.</td><td></td></tr><tr><td><strong>Issue type</strong></td><td>Include specific types of issues.</td><td></td></tr><tr><td><strong>Jira filter</strong></td><td>Add a <a href="https://support.atlassian.com/jira-software-cloud/docs/save-your-search-as-a-filter/">Jira filter</a>. See below for details.</td><td></td></tr></tbody></table>

#### Jira filter

To access more powerful filtering capabilities, you can add a [Jira filter](https://support.atlassian.com/jira-software-cloud/docs/save-your-search-as-a-filter/) to narrow down the list of issues. Using JQL and Jira's advanced filtering capabilities, Jira filters give you the ability to filter based on any available fields.

### JQL Mode

JQL mode gives you the full power of JQL without the need to create a Jira filter. To learn more about JQL and how to use it please, refer to the following documentation.

{% embed url="<https://support.atlassian.com/jira-service-management-cloud/docs/use-advanced-search-with-jira-query-language-jql/>" %}

{% embed url="<https://www.atlassian.com/software/jira/guides/jql/cheat-sheet#advanced-search>" %}


---

# Agent Instructions: 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/staging-area.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.