In UserRequest properties there is an "Dates" section with including "TTR Deadline" value. This value is basically a relative timer - a countdown from NOW to date defined in "ttr_100_deadline" column in SQL for specific UserRequest ID. "ttr_100_deadline" is "datetime" type of attribute and thus contains readable date and time when ticket reaches TTR SLA.
Now the question: how to change form of this "TTR Deadline" from "countdown" to exact datetime when ticket reaches TTR SLA? i.e. I would like to see absolute value (exact time) instead of relative value (countdown).
thanks
Last edit: michal.bruncko 2017-07-31
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you want to change a existing class you can write an extension for itop https://wiki.openitop.org/doku.php?id=2_3_0:customization:start.
Look in itop/env-production/itop-request-mgmt-itil/datamodel...
Copy the class and _delta="redefine" or only alter the needed field. You also could just add a new field with <class id="user-content-..." _delta="merge">
<field ...="" _delta="define"></field></class>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi med
thats something which I fully understand and use for all my customizations. but my request is a bit special due to fact, that "TTR Deadline" is AttributeSubItem which is a part of "AttributeStopWatch" class with which I am not too much familiar. You cant redefine "ttr_escalation_deadline" as because it will not work, but rather you have to redefine/adjust AttributeStopWatch class function behavior which is displaying "deadline" type of stopwatch requests and which could have impact to overal SLA computation which I dont wanted to break.
request is pretty easy: change the form of how TTR deadline is shown in user request(s). instead of having countdown I would like to have real deadline (exact datetime when TTR expires). but as I just said the implementation is actual not that easy like with adjusting another part(s) of datamodel.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ok, at the end I found that this "TTR Deadline" format is configurable via iTop configuration file :-) - with parameter 'deadline_format'. either it can be $difference$ (default vaule - the countdown) or $date$ (exact TTR expiration date).
thanks developers that you made this behavior such simply configurable ;-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In UserRequest properties there is an "Dates" section with including "TTR Deadline" value. This value is basically a relative timer - a countdown from NOW to date defined in "ttr_100_deadline" column in SQL for specific UserRequest ID. "ttr_100_deadline" is "datetime" type of attribute and thus contains readable date and time when ticket reaches TTR SLA.
Now the question: how to change form of this "TTR Deadline" from "countdown" to exact datetime when ticket reaches TTR SLA? i.e. I would like to see absolute value (exact time) instead of relative value (countdown).
thanks
Last edit: michal.bruncko 2017-07-31
If you want to change a existing class you can write an extension for itop https://wiki.openitop.org/doku.php?id=2_3_0:customization:start.
Look in itop/env-production/itop-request-mgmt-itil/datamodel...
Copy the class and _delta="redefine" or only alter the needed field. You also could just add a new field with <class id="user-content-..." _delta="merge">
<field ...="" _delta="define"></field></class>
hi med
thats something which I fully understand and use for all my customizations. but my request is a bit special due to fact, that "TTR Deadline" is AttributeSubItem which is a part of "AttributeStopWatch" class with which I am not too much familiar. You cant redefine "ttr_escalation_deadline" as because it will not work, but rather you have to redefine/adjust AttributeStopWatch class function behavior which is displaying "deadline" type of stopwatch requests and which could have impact to overal SLA computation which I dont wanted to break.
request is pretty easy: change the form of how TTR deadline is shown in user request(s). instead of having countdown I would like to have real deadline (exact datetime when TTR expires). but as I just said the implementation is actual not that easy like with adjusting another part(s) of datamodel.
ok, at the end I found that this "TTR Deadline" format is configurable via iTop configuration file :-) - with parameter 'deadline_format'. either it can be $difference$ (default vaule - the countdown) or $date$ (exact TTR expiration date).
thanks developers that you made this behavior such simply configurable ;-)
Thanks Michal for your feedbacks and implication. It helps us to know that our product is appreciated.
this is really great Vdumas
this is really great Vdumas