I'm sure this has been mentioned before but I thought I'd share it as it's a useful tip.

Ontime is set to work woth 8 hour days, we work based on a 7 hour day so when we were entering 1 day estimated time against a feature for example, the reports and Dashboard would calculate the number of hours incorrectly.  We found that by editing the TimeUnitTypes table in SQL Server and changing the value of the ConversionFactor field we could make OnTime work with a 7 hour day.  All you do is enter the number of minutes that makes up a day in the ConversionFactor field and hey presto! 

 

Dean,

Thanks for the tip...you have answered one of my outstanding questions.  However, I am wondering whether making such a manual edit to the database will affect any future application updates/upgrades, or visa-versa.  What does Axosoft Support say about this?

Great tip none-the-less!

---

Marc Gervais, MCAD

Hello Marc,

That particular field, the TimeUnitType, is really the only field we can support modifying manually in the tables.

I was told by one of our developers that changing that field won't have any adverse effect later on down the road.
 

---

Thank you,

Tom Harder
Axosoft Support
support@axosoft.com
1.800.653.0024 option 3
--'Fear the Bug' Podcast--

What about exposing this field in the System Options tab ? Is it still allowed to be modified manually ?