Hi! Thanks for the info Kenneth i will look into it further.
Joosep On Thu, May 5, 2011 at 5:43 PM, Kenneth Crocker <[email protected]> wrote: > Joosep, > > I would think the DB changes ARE necessary. If you don't define the field > with 3 decimal positions, then it would always round up or down and you'd > gain/lose a lot of time. We didn't like the option of hours or minutes, so I > removed the top-down choice. Since we offered hours in the form of .125 > days, we felt that should be sufficient. We didn't know of ANYONE in our > organization that would project time estimates in hours or minutes. Most > projects involve many, many man-days. > > Anyway, that was our thinking. > > Kenn > > > On Thu, May 5, 2011 at 7:06 AM, Joosep <[email protected]> wrote: > >> Thanks for the reply Kenneth, >> >> Is the database modification also necessary in order it to work, or should >> it work with just the modifications in the file >> local/html/Elements/SelectTimeUnits >> ? >> >> Implementing the code from that thread so far only seem to give the >> possibility to select days from the dropdown menu when using for example >> "time estimated" field in the ticket basics, but seem to lack the math. At >> least in RT 3.8.10. When inserting some value in hours, RT automatically >> converts the inserted value into minutes(for example inserting 2 hours >> results after save 120 minutes). When inserting for example 5 hours, after >> the save, it results in 5 minutes. >> I'm not very familiar with perl, but it seems that these rows should be >> responsible for the math: >> > % my $selected = 'minutes'; >> > % $selected = 'hours' if $minutes > 60; >> > % $selected = 'days' if $minutes > 480; >> >> But they don't seem to do it. Maybe the math has moved since then or i'm >> doing something wrong. >> I would be grateful for any pointers and hints where to look. >> >> Thanks in advance >> Joosep >> >> >
