> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/support-workflows/issues/issue-groups.md).

# Issue Groups

Group related issues together during incidents

Issue groups introduce a parent-child relationship between issues and a new interface to manage the parent issue, including:

* Seeing all the associated child issues and being able to navigate to them
* Sending a bulk reply to all child issues, for example an outage resolution message
* When closing an issue group, optionally close all child issues at once.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2Fy0ePU2Z28ZkLdGFGNFZp%2FCleanShot%202025-05-08%20at%2000.59.43%402x.png?alt=media&amp;token=dc8a8736-1811-4653-b350-51baca296caa" alt=""><figcaption></figcaption></figure>

## Filter issue groups in views

| Filter                     | What it matches                                                                                                          |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Is Issue Group**         | Issue groups themselves.                                                                                                 |
| **Number of Child Issues** | Issue groups, by how many child issues they have.                                                                        |
| **Parent Issue Group**     | **has any value** matches child issues. **has no value** matches everything else, including the issue groups themselves. |

To keep child issues out of a view while still seeing each issue group, add **Parent Issue Group** · **has no value**. To hide the issue groups as well, also set **Is Issue Group** to **No**.


---

# 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.usepylon.com/pylon-docs/support-workflows/issues/issue-groups.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.