Retain Actual Time Data of Removed Users in Reporting

English Forum Product Feedback
, ,
1

Issue: Asana’s Actual Time field is useful for time tracking, but suffers from a serious reporting limitation when users leave the organization. The Pause License feature partially mitigates the reporting issue, but is limited to 10% of the license count.

Example scenario: JaneD leaves the organization, and has hundreds of hours of Actual Time logged to Projects across several Teams. The admin Removes JaneD’s account in Asana. The org wishes to create an end of year report for TeamXYZ, but notices the expected total hours are missing JaneD’s Actual Time, creating a reporting issue. The admin then changes JaneD’s Asana account status to Paused, which reactivates Actual Time data, and corrects the shortage in the report.

The Problem: Other users have also left the org, creating additional missing Actual Time totals in the report. Attempting to set these additional former users to Paused status causes an error message, due to a limit on the number of Paused users allowed in an org, as per the documentation here:

https://help.asana.com/s/article/pause-a-member-s-license?language=en_US

Feature Request: either allow more Paused users, or allow Removed user Actual Time data to be available to reports.

2

Additional Perspective: Actual Time should be immutable. Time tracking is often used to track billable hours. Billable hours should never walk out the door with former staff.

The current implementation of Actual Time has a critical flaw for this reason. Actual Time logged to a project must remain visible, regardless of member account status.

Fix: The ledger for a Project’s Actual Time entries should be decoupled from member account status. Optionally, include a toggle to show or hide deactivated users’ Actual Time entries when creating reports.

Related feedback: Paused users can reactivate their accounts, by simply logging in. Additionally, plan tiers below Enterprise lack admin level password resets for members. This combination makes the Pause status effectively unusable, since former staff using Asana on a personal mobile device will trigger Paused user account reactivation. This makes the Paused user workaround for reporting rather problematic.

1 Like