If anyone has any ideas, I would greatly appreciate hearing
them. I've spent a good amount of time trying to debug
what is going on here and come up empty-handed so far.
On 8/18/2011 1:35 PM, Jeff Blaine wrote:
RT 3.8.7 in production
RT 3.8.10 in development
This has been a long-standing oddity. For a brand new
ticket, note the difference between the fill-in text
AffectedEmployeeDetails field below and the other
fill-in-text fields:
==
[-- Basics --]
blah blah
blah blah
[-- Custom Fields --]
AffectedEmployeeNumbers: (no value)
AffectedEmployeeDetails:
Scope: (no value)
Details: (no value)
==
Can anyone explain that? We do absolutely nothing with
any of those fields at ticket-creation time. It's a
problem (minor) because the first time someone modifies
any field and saves, a bogus/confusing line appears as
a notice:
* is no longer a value for AffectedEmployeeDetails
Then, and only then, does AffectedEmployeeDetails show
as having (no value) like the others.
RT Training Sessions (http://bestpractical.com/services/training.html)
* Chicago, IL, USA September 26 27, 2011
* San Francisco, CA, USA October 18 19, 2011
* Washington DC, USA October 31 November 1, 2011
* Melbourne VIC, Australia November 28 29, 2011
* Barcelona, Spain November 28 29, 2011
RT Training Sessions (http://bestpractical.com/services/training.html)
* Chicago, IL, USA September 26 27, 2011
* San Francisco, CA, USA October 18 19, 2011
* Washington DC, USA October 31 November 1, 2011
* Melbourne VIC, Australia November 28 29, 2011
* Barcelona, Spain November 28 29, 2011
