Currently, we experience users entering time for work that is long term in progress months after doing the work, for example time entry for 1/03/2023 on 31/05/2023. OR they are editing time from start of the year and increasing hours for work that is still in progress.
This has a major impact on our reporting, as we lock out previous months. Despite process and rules around adding and adjusting times for previous months, it would be good to prevent this type of time entry, just like the functionality around not being able to add time to closed work items after x hours.
The functionality for not being able to add time to work items that are closed, our users still add time to these work items, they change the state to Active/New, add their time and close the work item again, so the work that was closed months ago, still has time being added to it significantly late.
This additional feature will fix
- The issue that we see for closed work item time entry increasing (change state work around) and
- Back dating time entry into work items.
Thank you.
-
Hello Rodney,
Thank you for reaching out. Are you familiar with our approval functionality? This feature allows you to lock weeks for editing, preventing users from modifying or adding worklogs for a given week. You can find detailed information in our documentation: https://support.7pace.com/hc/en-us/articles/115000580146-7pace-Timetracker-s-Approval-Page-#Locking%20weeks%20for%20editing
If this option doesn't suit your needs, I can only suggest exploring ways to prevent reopening items within Azure DevOps itself. In general, we are very cautious about enabling very strict rules that could reduce the flexibility of teams, but I will mark this thread as 'Gathering feedback' so we can capture the interest of others users.
All the best, Nici
Please sign in to leave a comment.
Comments
1 comment