<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label. For the Community Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug For the Enterprise Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary `timeago` determines the number of passed months incorrectly ### Steps to reproduce Given that today is the 20th of March 2019, the issues opened on 19th of December 2018. I suspect, the issue appears when the February (as the shortest month) lays inside the considering period. ### Example Project Originally this issue was found on the company's internal GitLab installation (GitLab Enterprise Edition 11.8.1-ee) and then reproduced on the Gitlab.com itself so I assume the issue persists in the latest version. ### What is the current *bug* behavior? Given that today is the 20th of March 2019, the issues opened on 19th of December 2018 are displayed as "opened 2 months ago". For example, https://gitlab.com/gitlab-org/gitlab-ce/issues/55562. ### What is the expected *correct* behavior? The correct behavior would be to display "opened 3 months ago". ### Relevant logs and/or screenshots