Repository navigation
Conversation
…time * time calculation was wrong, as it did not consider negative time frames (startTime after endTime) * using same logic now like for work time calculation
Collaborator
Author
|
Maybe it would be more obvious for the user when the negative time is shown in the work items. If this is done have a look at the report timeline, as this will most likely not work with negative times. Instead of hiding the wrong start end time selection by just using the abs() method (like it was fixed now). |
JSchraff
reviewed
Apr 14, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes issue where time was calculated wrong in report for the whole project, when work items exist which have startTime after endTime.
Issue was in Controller.calcSeconds but I also adapted logic at the other places