---
title: "Release 5.19.4"
description: "Legacy shared filters are visible to operators again and open in the editor with all their conditions; Fast Line Pro agents are available again on instances with Dify v2."
---

# Release 5.19.4

Release 5.19.4 includes all changes of releases [5.19.1](/en/releases/5.19.1.md), [5.19.2](/en/releases/5.19.2.md) and [5.19.3](/en/releases/5.19.3.md). New in 5.19.4 are fixes to shared filters in the operator panel and the return of Fast Line Pro agents that had disappeared from the list on instances with Dify v2.

## Operator panel

**New**

- **"Ticket status" and "Bot" conditions in the filter condition builder.** The shared filter editor (**Settings → Operator panel → Operator Line filters and view**) now has **"Ticket status"** and **"Bot"** conditions. They are also available in the condition builder of the operator panel quick filter.

**Fixed**

- **Shared filters created before the new shared filters page are visible to all operators again.** After the shared filters page was turned on, public filters of the old kind were visible only to their author. Such filters are now visible to all operators again, with no manual audience setup.
- **The shared filter editor shows the conditions of old filters.** Previously a filter saved before the new page opened empty, the **Save** button was inactive, and saving after adding a condition erased the old conditions. Now:
  - old filters open with all their conditions: ticket statuses, bot, assignees;
  - an old public filter that has not been re-saved opens with the **"All operators"** audience;
  - conditions that the form fields do not cover are shown as a read-only list and saved unchanged;
  - if the conditions of an old filter cannot be read, the editor shows a warning, leaves the conditions untouched and lets you save the other settings;
  - such a filter can be published, including after archiving and restoring.

## Fast Line Pro

**Fixed**

- **Fast Line Pro agents are visible in the list again.** On instances with Dify v2 the agent list could become empty, and the Fast Line action in scenarios failed with the error "Agent … not found". Agents are now displayed in ConnectiveOne again, and scenarios that use them respond.

## Related documentation

- [Manage shared filters and the default Operator Line view](/en/operatorline/how-to/manage-shared-filters.md)