---
title: "JIRA Notifications"
canonical: "https://documentation.chaos.com/space/DOCSGUIDE/1114537986/JIRA%20Notifications"
format: markdown
---
This page provides information about Notifications set for the **DOC** Jira project.


## **Overview**

---

Since the process in the PDIX team includes colleagues from other teams, we need to inform them properly and on time about the progress of the logged task. The changes from *July-August 2026* refer to:

- **QA Assignee** field
- **All Watchers **field

> ℹ️ To understand better why these changes were needed, see the [Reasons](#Reasons) section below.


## **QA Assignee notifications**

---

According to the created *Automation flows*, the person added to the **QA Assignee** field:

- is automatically added to the Watchers list
- receives a personal e-mail about being added as a QA Assignee of the particular ticket
- receives a reminder (personal e-mail) if the ticket was moved to a QA status *a week ago* and no action has been taken, including also a note to change the status to **Publishable**
- receives a reminder (personal e-mail) if the ticket was moved to a QA status *a month ago* and no action has been taken, including also a note to change the status to **Publishable**


## **All Watchers notifications**

---

After acknowledging the **Notification sheme** of the **DOC** Jira project (used for all PDIX tasks), the following changes were applied from August 11, 2026 onward.

Add **All Watchers** as recipients for these event types:

- A work item is updated by a workflow transition (generic event)
- A work item is resolved
- A work item is closed
- A work item is reopened
- A work item is edited


## **Reasons**

---

After analyzing the PDIX workflow for the last few months, the following issues were detected:

⚠️ Tickets stay in QA status for too long.

⚠️ Colleagues are not always aware that they have been added as a QA Assignee to a ticket, or they often forget.

⚠️ A lot of manual personal reminders (Jira comments, private messages, group messages) were made.

⚠️ The DOC Jira project had limited notifications compared to other Jira projects, and task progress was hard for external colleagues to follow.

⚠️ Colleagues from other teams do not change the status from QA to Publishable themselves, as we expect.