Skip Navigation LinksHome Page > Forums > Announcements > Rants and Raves > New Feature Request
My client has a couple of multi-year projects with a large number of defects (thousands). I have just added some custom fields to help with analysis and populated them with the respective values (via the Bulk Edit capability).
Some of the defects have not been touched in a significant time, but unfortunately, adding the analysis values has set the "Last Updated" field to yesterday (when I applied the field).
I would like a way of updating records in a way that does not update the "Last Updated" field, or to reset it after I have made the change. This could be, for example, by adding an attribute to custom fields to indicate that they are not to update "Last Updated" (they fall into a "non-core" category, perhaps).
Hi Colin
I'm afraid for audit purposes that is not possible through the UI or the API.
You would need to make any such updates directly in the database (which is not officially supported, but would work in this case).
Regards
David
You can execute raw SQL queries to update the fields directly without affecting the timestamps. This method bypasses the ORM and its automatic timestamp handling:
UPDATE your_tableSET custom_field = 'value'WHERE conditionspace waves
I have similar problem.
We have some technical fields that are updated from git/quality control tools.
So, I would like to be able to exclude some custom fields from being tracked in a history and from changing "Last Updated" field.
It is possible to update the record in a way that does not update the "Last Updated" field or reset the field after making changes but the history may still be retained fish eat fish
Hi Elliot,
As David said, for audit purposes that is not possible through the UI or the API.
Regards,
Kat
And if you have any questions, please email or call us at +1 (202) 558-6885
