| Reporter |
Dan Lyons (dan.lyons)
|
|---|---|
| Created | Apr 5, 2013 11:20:49 PM |
| Updated | Apr 5, 2013 11:20:49 PM |
| Priority | Normal |
| Type | Bug |
| State | Open |
| Assignee | Pavel Nikolaev (pasha) |
| Subsystem | Time Tracking |
| Fix versions | No Fix versions |
| Fixed in builds | No Fixed in build |
| Affected versions | No Affected versions |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
What steps will reproduce the problem?
1. Open the command dialog on an issue
2. Attempt to add work to the issue using the add work Today <period> overload
3.
What is the expected result?
Since I am using the date identifier Today, I would expect it to resolve to the correct date (currently 2013-04-05)
What happens instead?
The date resolves to yesterday (2013-04-04)
Please provide any additional information below.
Attach a screenshot if possible
I ran across this because I just updated our workflow rules to perform automatic time tracking based upon state transitions. One of my teammates pointed out that the dates used for the time tracking were from yesterday. The workflow rule I added uses the same command as the jetbrains-youtrack-statesWorkTimer's Stop timer: state becomes 'Fixed' rule.
I played around with the command in the add command window and noticed the same behavior (see attached).
A workaround for now is to omit Today, as the date appears to be optional and will automatically resolve to today's date.
1. Open the command dialog on an issue
2. Attempt to add work to the issue using the add work Today <period> overload
3.
What is the expected result?
Since I am using the date identifier Today, I would expect it to resolve to the correct date (currently 2013-04-05)
What happens instead?
The date resolves to yesterday (2013-04-04)
Please provide any additional information below.
Attach a screenshot if possible
I ran across this because I just updated our workflow rules to perform automatic time tracking based upon state transitions. One of my teammates pointed out that the dates used for the time tracking were from yesterday. The workflow rule I added uses the same command as the jetbrains-youtrack-statesWorkTimer's Stop timer: state becomes 'Fixed' rule.
I played around with the command in the add command window and noticed the same behavior (see attached).
A workaround for now is to omit Today, as the date appears to be optional and will automatically resolve to today's date.