custom fields blanked on update
Posted: 26 Sep 2005, 16:58
(1.0.0-rc1)
When a user updates a bug, it appears that enumerated custom fields are blanked. What's even more confusing is that it appears that this only happens some of the time.
For example, if a bug is entered with the enumerated custom field A set to B, when another user views that bug and then hits the 'Update Issue' button, on the update page field A will be set to blank/null. Thus, when the user then hits the 'Update Information' button to save their changes, field A will lose its value.
Our solution for this is going to be moving from enumerated to text fields which is less than ideal.
Any ideas on a cause or solution?
When a user updates a bug, it appears that enumerated custom fields are blanked. What's even more confusing is that it appears that this only happens some of the time.
For example, if a bug is entered with the enumerated custom field A set to B, when another user views that bug and then hits the 'Update Issue' button, on the update page field A will be set to blank/null. Thus, when the user then hits the 'Update Information' button to save their changes, field A will lose its value.
Our solution for this is going to be moving from enumerated to text fields which is less than ideal.
Any ideas on a cause or solution?