The current UI tracks both acknowledgment and response tasks under a single “Overdue” filter. However, acknowledgment due dates may not be the most meaningful indicator of overdue work, as the primary focus is typically on whether assigned reviewers have completed their required responses. It would be beneficial to provide an option to track acknowledgment and response tasks separately, allowing users to better prioritize their work. While this distinction is currently available through export reports or the Insights dashboard, these are accessed through a different UI, whereas users generally prefer to filter and manage tasks directly within their primary workspace.
|
Practical use of functionality?
Provide an option to track and filter acknowledgment and response tasks separately within the Overdue view. This would allow users to focus on response‑related delays while still retaining visibility into acknowledgment tasks if needed. Although this distinction is available in export reports and the Insights dashboard, exposing it directly in the primary workspace aligns better with how users manage their day‑to‑day tasks. |
|
|
What is the impact of not doing this?
Separating acknowledgment and response overdue tasks improves clarity and prioritization for users managing packages. Teams can quickly identify blockers that affect progress, reduce unnecessary follow‑ups, and focus on actions that matter most. By surfacing this distinction directly in the main UI, users can work more efficiently without relying on secondary reporting tools. |