Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #5422
Closed
Open
Issue created Mar 13, 2017 by bmortier@bmortierMaintainer

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
Assignee
Assign to
Time tracking