Summary
Currently, task filter queries require hardcoding specific usernames when filtering by assignees (e.g., assignees = alice or assignees in alice, bob). When sharing project views or saved filter templates across a team, this requires every team member to create and maintain their own individual filters to see tasks assigned to them.
Proposed Solution
Support @me, currentUser, and current_user dynamic macros in task filter query strings.
When a query containing assignees in @me or assignees = currentUser is evaluated, the backend filter engine dynamically resolves the macro to the authenticated user's username (web.Auth).
Use Cases
- Shared project views (e.g. "My Tasks" view in a shared project) where each team member views their own assigned tasks dynamically.
- Saved filter templates across organizations.
Summary
Currently, task filter queries require hardcoding specific usernames when filtering by assignees (e.g.,
assignees = aliceorassignees in alice, bob). When sharing project views or saved filter templates across a team, this requires every team member to create and maintain their own individual filters to see tasks assigned to them.Proposed Solution
Support
@me,currentUser, andcurrent_userdynamic macros in task filter query strings.When a query containing
assignees in @meorassignees = currentUseris evaluated, the backend filter engine dynamically resolves the macro to the authenticated user's username (web.Auth).Use Cases