Ability to prevent the time tracked to a task on one project from being transferred and double counted on a user's timesheet when that task has been moved to another project
C
Christina Warnock
We’ve detected a situation where when a task is moved with time tracked against it from one project to another, and the timesheet has not yet been submitted, that time automatically shows up on their timesheet. When that task is then moved to a new project, the time tracked travels with it and is counted again, doubling the time tracked for 1 task on the timesheet, when in actuality, that time should have been only applied to the project that the time was originally tracked to. This feature request is for Hive to recognize when time is tracked to a task that it stays with the project it was tracked to. When a task with time tracked to it is moved to a new project, Hive should recognize the time was already tracked and reset time tracking in the new project.
Log In
Kelley Bunge
open
Kelley Bunge
in progress
Gina Lockwood
Merged in a post:
Moving an action with tracked time from one project to another causing doubled time in Timesheets
C
Christina Warnock
If a user had tracked time to a task while it was living in one project, but then the task is moved to another project, the time tracked is then doubled on the timesheet as it is counting the time tracked while it was in the initial project and again when it is in the new project in the total hours for the week.
Gina Lockwood
under review
R
Rick Bubenik
Yes, Yes, Yes! It will solve a lot of issues.
C
Christina Warnock
This feature will help avoid timesheets from being incorrect since the time tracked is doubling up in this scenario.