# Filter Incidents ## Filters Incidents To filter incidents, 1. Go to the **Incident List page** -> Choose the desired team from the available options. 2. Locate and click on the **Filter icon** -> Apply the desired combination of filters by selecting options such as **Created at**, **Responders**, **Tags**, etc. 3. Once you have set your filters, click on the **Apply** button.

Filter Incidents in Squadcast for Incident Management — Image. Filter Incidents

## Filters Below is a comprehensive list of filters accessible on the Incident Page:

Filter Name	Description
Assignee	Allows you to filter Incidents based on Responders. They can be Users, Squads, or Escalation Policies. Note: The Responder filter's scope encompasses all current and previous responders.
Created	Allows you to filter Incidents based on their Created Date. Note: By default, the Incident Page shows Incidents created in the last 7 days. Note: You will be limited to choosing the custom time range here based on the plan that you are currently on (data retention by the plan). Here are the options for this filter: 1. Last 24 Hours - shows incidents for the last 24 hours. 2. This Week - shows incidents from the beginning of the week (Sunday) to now. 3. This Month - shows incidents from the beginning of the month to now. 4. Last 7 Days - shows incidents from exactly the last 7 days. For instance, if a user queries this filter at 17:30 p.m. on 10/10/2023, it will show incidents from 17:30 p.m. on 3/10/2023 to 17:30 p.m. on 10/10/2023. 5. Last 14 Days - similar logic to the "Last 7 Days" filter. 6. Last 30 Days - similar logic to the "Last 7 Days" filter.
Service Owner	Allows you to filter incidents that affect services owned by specific squads or users Eg: You can use this filter to find incidents that affect services owned by your squads
Services	Allows you to filter Incidents based on their respective Services.
Tags	Allows you to filter Incidents based on Tags. Note: Without any Service filter, all Tags across Services are displayed. To narrow down Tags by Service, apply the Service filter first. Note: Multiple Tag Filters Selecting multiple Tag values functions as a logical `AND` operation. To view the list of Incidents for each Tag, perform the selection in multiple steps.
Alert Sources	Allows you to filter Incidents based on Alert Sources. Note: The drop-down shows the valid Alert Sources for the selected date range.
SLO Affecting	Allows you to filter Incidents based on the SLOs affected by them.
Show Incidents with Postmortem	Allows you to filter Incidents based on whether they contain a Postmortem or not. Note: For incidents with a Postmortem, you can further filter the list by their statuses, namely: In Progress, Under Review, and Published.
Show Incidents with Notes	Allows you to filter Incidents based on whether they contain a Note or not.
Show Starred Incidents	Allows you to filter important Incidents that have been starred.

{% hint style="info" %} Note: * You can select multiple options per filters, and type in, to search and refine your choices. * We use "AND" for combining filters and "OR" for each filter condition. {% endhint %} ## Find incidents relevant to your squads ### Incidents assigned to you or your squads: * Your squads are shown at the top of the Assignee dropdown * You can click on 'select all' to view incidents assigned to you or your squads

### Incidents that affect services owned by you or your squads: * Your squads are shown at the top of the Service Owner dropdown * You can click on 'select all' to view incidents that affect services owned by your or your squads

*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.* --- # 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://support.squadcast.com/incident-list/filter-incidents.md?ask= ``` 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.