There seems to be a problem with TimeAttribute

In FD 1.0.19 TimeAttribute instances appear empty when opening an object even if saving seems to work. This concerns DHCP, DNS and ppolicy as far as I know (was only able to test DNS on demo-fixes).

(from redmine: issue id 5422, created on 2017-03-13, closed on 2017-03-16)

• Changesets:
  • Revision ae5284fd by Côme Chilliet on 2017-03-13T12:46:57.000Z:

Fixes #5422 Fixing UnitIntAttribute broken since 1.0.18

See commit 334eca1541e354999d7fe72551ff062de51646b2

• Revision 9152f86b by Côme Chilliet on 2017-03-13T12:48:44.000Z:

Fixes #5422 Fixing UnitIntAttribute broken since 1.0.18

See commit 334eca1541e354999d7fe72551ff062de51646b2

• Custom Fields:
  • Support contract: None
  • Dolibarr project Name: PJ1610-0019

This because of commit 334eca15 so it’s been there since 1.0.18 it seems.

(from redmine: written on 2017-03-13)

By Côme Chilliet on 2017-09-02T15:36:02 (imported from GitLab)

Reverted the «fix»

(from redmine: written on 2017-03-13)

By Côme Chilliet on 2017-09-02T15:36:03 (imported from GitLab)

Close issue

(from redmine: written on 2017-03-16)

By Côme Chilliet on 2017-09-02T15:36:03 (imported from GitLab)

Set time spent

(from redmine: written on 2017-06-22)

By Côme Chilliet on 2017-09-02T15:36:03 (imported from GitLab)

closed

By Côme Chilliet on 2017-09-02T15:36:03 (imported from GitLab)

added 1h of time spent

By Côme Chilliet on 2017-09-02T15:36:04 (imported from GitLab)

added Fixed label

By bmortier on 2018-09-25T15:52:45 (imported from GitLab)