If you modify the code in place, your changes will get overwritten when
you upgrade (even a minor upgrade). In general, options for changes are:
1) Change in place. Will get squashed on upgrade, so keep a copy
somewhere and make a note to reapply after upgrades.
2) Create a local directory in your rt directory and override (duplicate
the directory structure and file under local).
3) Use callbacks which add to the code without overriding.
4) Create an extension using the techniques above to manage the changes
in a separate package (and possibly share with others).
Any of the above will work for making custom changes. I think an
extension that allows you to set a preferred format via config and then
uses that over the default in DurationAsString would be very useful. (RT
features often begin life as extensions, then get pulled into core.)
On 2/1/16 3:17 PM, Matt Zagrabelny wrote:
On Mon, Feb 1, 2016 at 2:08 PM, Keith Creasy <[email protected]> wrote:
I do see in the code how to display the TimeLeft in minutes. Now I wonder if I
want to modify the file in ./share/html/Elements/RT__Ticket/ColumnMap.
I wouldn't.
Should this be done in a local callback?
This is what I'd do.
-m
---------
RT 4.4 and RTIR Training Sessions
(http://bestpractical.com/services/training.html)
* Hamburg Germany March 14 & 15, 2016
---------
RT 4.4 and RTIR Training Sessions
(http://bestpractical.com/services/training.html)
* Hamburg Germany March 14 & 15, 2016
