If this item should be posted in RT Users, I would be glad to do that.
Subject: RT 6.0.2 - Global Custom Field Value Cleared When Changing Queue on Child Ticket Create
Hello,
I'd like to report a bug I've found in RT 6.0.2 involving global custom fields being cleared when the queue is changed during child ticket creation.
**Environment:**
- RT Version: 6.0.2
- Web server: Nginx (reverse proxy) → Starman
- Database: MySQL
**Steps to Reproduce:**
1. Open a parent ticket
2. Create a child/sub ticket using the ticket create form
3. A global custom field is preset with a value (either via a default value or pre-population from the parent)
4. Change the Queue dropdown to a different queue on the create form
5. Observe the global custom field value
**Expected Behavior:**
The global custom field value should be preserved when changing queues, since the field is global and applies to all queues.
**Actual Behavior:**
The global custom field value is cleared/emptied after the queue is changed. The field box becomes empty and the previously set value is lost.
**Additional Context:**
This appears to be related to RT 6's HTMX-based queue change behavior. When the queue is changed, RT triggers a reload of the create form widgets (via `QueueChanged=1`), and the global custom field widget appears to be re-rendered without preserving the previously entered value.
A similar issue was fixed in RT 6.0.1 for the Description field ("Preserve Description field content when changing queues on ticket create/update pages"), but the same fix does not appear to have been applied to global custom fields.
Please let me know if you need any additional information, logs, or a HAR file to help diagnose this issue.
Thank you.