# 2023-10-13: Product Update

| **Date**                | **Action**                                                                                                     |
| ----------------------- | -------------------------------------------------------------------------------------------------------------- |
| 2023/10/13 at 17:00 EST | <p>What’s Happening</p><p>·       UX Update deployed</p><p>Impact to your data</p><p>·       None expected</p> |

This release adds minor UX and functional improvements based on stakeholder feedback, in particular.

**Role Administration**

* Bug resolved where user rights would not populate for Roles

**Ticketing**

* Ticket window description box now expands to the full usable size supported by the window
* Avatars for Reveald synchronized tickets now more prominently differentiate content from internal user comments
* Bug resolved where Ticket Table download would create a zero byte file
* Reveald JIRA ticket number now searchable from the ticket table search box, using a string search of ‘RCS-xxx’ or an exact search of jira\_id: ‘RCS\*’ etc.

**Attack Path Tools**

&#x20;Vulnerabilities

* Bug resolved where Tables of devices accessed by clicking the counts in the “Devices in Paths” and “Affected Devices” did not properly filter to the required devices

Impact Matrix

* The impact matrix table now supports a configurable number of rows

This launch is not expected to disrupt or change working practices.


---

# 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.reveald.com/technical-documentation/changelog/2023-10-13-product-update.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.
