estimate quick action does not produce correct time for 1mo
When you use the
/estimate 1mo quick action (or some other multiple of months), the resulting time listed under
Time tracking is actually set to 1 month and 2 weeks.
Steps to reproduce
Create a new issue. In the description, place
/estimate 1mo on its own line. Then, either preview the text or submit it. You will see that the time estimate will actually be set to
1mo 2w instead of just
The same behavior can be seen in other places, for example using the quick action in a comment.
I just created the following issue demonstrating the problem: kmorel/example-project#1
What is the current bug behavior?
When you enter a time estimate of 1 month, you get a value of 1 month and 2 weeks. Likewise, a time estimate of 2 months will give you a value of 3 months. The time appears to be inflated by 50%.
What is the expected correct behavior?
When you enter
/estimate 1mo the estimated time should be set to
Relevant logs and/or screenshots
Output of checks
This bug happens on Gitlab.com.
(I first observed it on an instance of GitLab Community Edition, but I can see the same behavior on gitlab.com.)
Results of GitLab environment info
Results of GitLab application Check
I have not looked at any of the implementation, but what I suspect is happening, is that when you enter
/estimate 1mo, it is converting 1 month into around 30 days. Then, when the time estimate is printed, it is interpreting those 30 days on a 5 day per week work schedule, which would turn those 30 days into 6 weeks. Assuming 4 weeks is about 1 month, that gives you the unexpected result of 1 month and 2 weeks.