Opened 19 years ago
Closed 18 years ago
#1809 closed defect (worksforme)
Component field on ticket keeps resetting itself
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | 0.8.3 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
We have several tickets in Trac that keep resetting their component fields to the first component in the list whenever the ticket is edited. Each time you pull up one of these tickets, the Component drop-down list shows the first Component in the list, not the actual Component value set on the ticket. This means if the user changes any data on the ticket and hits submit, the Component will be reset to the first Component in the Component list (unless the user notices that the drop down is incorrect and changes it to the right Component). If the user does change the Component drop down to the right Component and hits submit, the Component field will be right on the ticket, but the drop-down will be set to the first Component in the list again. There seems to be no way to keep the drop-down consistent with the ticket's actual Component, nor any way to get the offending tickets out of this strange state.
The two tickets seemed to get into this state when the admin was editing the Component list through trac admin while a user had the ticket open. The user then submitted a change to the ticket, which put the ticket into this state. One of the tickets' Component field was changed in the offending edit, but the other ticket's edit did not touch the Component field at all.
This problem might have been due to a broken web browser… anyway, it's probably not relevant anymore.