Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G g1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 68
    • Issues 68
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cto
  • g1
  • Issues
  • #159

Closed
Open
Created Mar 28, 2019 by S Anand@s.anandOwner

FormHandler table parses dates in the wrong time zone

  • My birthday is on 23 Nov.
  • datetime.datetime(2019, 11, 23).timestamp() == 1574485200. I get the same timestamp if I save the cell in Excel as a date and read it
  • FormHandler parses Excel files with this date and returns 1574485200000
  • moment(1574485200000).toString() == "Fri Nov 22 2019 19:00:00 GMT-0500" in New York
  • moment.utc(1574467200000).toString() == "Sat Nov 23 2019 00:00:00 GMT+0000" in New York and in India

Hence, use moment.utc() instead of moment() when parsing dates from FormHandler

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking