Drew,
You are correct. I am not (at this time) interested in the change of the
value of a custom field within a ticket. It is the name of the field, as
changed from the configuration menu of the UI, that I am interested in
tracking. And, as you point out, there are history links for many similar
fields. This seems like a logical field to keep track of also.
Or, perhaps, I am using the field incorrectly, so, maybe this should be a
non-issue?
My use is that I have some 80 sites, across a half dozen business units
that a ticket might come from. So, on ticket creation the user selects from a
custom field (a drop down menu in the UI) his business unit, and then his
location. And, also, as a second CF, his application and problem. Is this
an unusual way of doing it? Is there a better way?
Anyways, someone changed the application menu by mistake. We have
recovered the contents from backup, so not a big deal as far as data is
concerned. But, the question is; shouldn't this data be tracked? And, it
appears that it is, partially. Who changed it, and when is clearly recorded
(for the last change, only). Just not what they changed it from, or to.
Anything relating to changing a ticket, or user, is tracked with the
transaction table. Either the changes in the internal (predefined) data
could go there, also, or, into a separate table. For most installations, I
would think this data is relatively static - IE, we don't add new sites all
that often - but, it does happen. And, new applications are relatively common
to us.
Thanks
Scott
I think the issue is a matter of understanding. From reading his messages I
get the impression that someone has, in the UI, changed the Name of the custom
field.
I don't know where this information could be kept, although I am seeing a
History link for Users which logs password changes and information changes.
Perhaps this could be extended for custom fields also?
On 8/31/09 6:48 PM, "Ken Crocker" <kfcroc...@lbl.gov> wrote:
Scott,
That can't be. I use the transaction record to trigger several scrips that look
at the changes in a CF. Try transactions with Type = "CustomField", Field =
the number of the CF and old/new values.
Kenn
LBNL
On 8/31/2009 2:32 PM, Lander, Scott wrote:
Hi Ken,
Transaction table was my first guess - but, nope - looks like everything BUT
the Custom Fields is kept there! Right now, I am thinking that for some
reason this data is just not kept - which sort of surprises me! Oh well -
time for a bug report or wish list submission, I guess!!!
Scott,
Try the Transaction Table.
Kenn
LBNL
On 8/31/2009 1:58 PM, Lander, Scott wrote:
Ken,
CustomFieldValues does have the current values, and documents when they were
inserted or modified, but, NOT the actual changes - IE, no "Old Value / New
Value". For instance, for one of the lines in question, the table has:
+-----+-------------+----------------------------------------------------------+-----------------------------+-----------+---------+---------------------+---------------+---------------------+
| id | CustomField | Name
| Description | SortOrder | Creator | Created |
LastUpdatedBy | LastUpdated |
+-----+-------------+----------------------------------------------------------+-----------------------------+-----------+---------+---------------------+---------------+---------------------+
| 321 | 30 | CPU |
| 4 | 101 | 2009-08-05 14:44:16 |
101 | 2009-08-24 19:56:54 |
What I need to find out is what the Name used to be! It shouldn't be CPU, at
one time (last week) it was something more like "NAS Storage".
Scott,
That's because the ObjectCustomFieldValues Table is for changes to a value for
an OBJECT. To see the history for the Custom Fields themselves, try
CustomFieldValues.
Kenn
LBNL
On 8/31/2009 1:45 PM, Lander, Scott wrote:
Gene,
Thanks, but - as near as I can tell, ObjectCustomFieldValues has references
from type RT::Ticket only. IE, everything in it refers to a ticket change,
not a global custom field change.
Scott
Scott, look in the ObjectCustomFieldValues table. There are pointers into it
from the OldReference and NewReference
fields in the Transactions table. I'm using 3.6.3, but I'm guessing that the
same will be true in 3.8.4.
Gene
Lander, Scott wrote:
We accidentally changed some values in a Custom Field, and they need to
be set back. I can retrieve the values from our backup, but, the
question came up of if RT keeps the history for them. Poking thru the
database, I see it keeps the history for tickets (table Transactions),
and that it keeps most of the data for Custom Fields in the table
CustomFieldValues. It keeps Creator, Creation Date, Last Updated By
and Last Update Date. But, so far, I haven't found anywhere it keeps
what was changed. IE, category old value, new value, like you find
in the Transactions table.
This would seem to be very useful information to have - especially in
the case of a system audit.
Am I just missing something?
This in on RT 3.8.4, btw.
------------------------------------------------------------------------------------
This e-mail message is intended only for the personal use of the recipient(s)
named above. If you are not an intended recipient, you may not review, copy or
distribute this message. If you have received this communication in error,
please notify the Hearst Service Center (cad...@hearstsc.com) immediately by
email and delete the original message.
------------------------------------------------------------------------------------
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
------------------------------------------------------------------------------------
This e-mail message is intended only for the personal use of the recipient(s)
named above. If you are not an intended recipient, you may not review, copy or
distribute this message. If you have received this communication in error,
please notify the Hearst Service Center (cad...@hearstsc.com) immediately by
email and delete the original message.
------------------------------------------------------------------------------------
________________________________
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
------------------------------------------------------------------------------------
This e-mail message is intended only for the personal use of the recipient(s)
named above. If you are not an intended recipient, you may not review, copy or
distribute this message. If you have received this communication in error,
please notify the Hearst Service Center (cad...@hearstsc.com) immediately by
email and delete the original message.
------------------------------------------------------------------------------------
________________________________
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
________________________________
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
--
Drew Barnes
Applications Analyst
Network Resources Dept.
Raymond Walters College
------------------------------------------------------------------------------------
This e-mail message is intended only for the personal use of the recipient(s)
named above. If you are not an intended recipient, you may not review, copy or
distribute this message. If you have received this communication in error,
please notify the Hearst Service Center (cad...@hearstsc.com) immediately by
email and delete the original message.
------------------------------------------------------------------------------------
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
