What is your set up?
Self Hosted Docker (Kubernetes)
Is your feature request related to a problem? Please describe
We run self-hosted Leantime as the system of record for a small multi-agent PM workflow (Cursor agents coordinating tickets, checkpoints, and handoffs via JSON-RPC / MCP). Watcher jobs need “only tickets updated since T” and “only In Progress / statusType=INPROGRESS”, but Tickets.getAll has no reliable modifiedAfter, so clients must pull large payloads and filter locally. That floods agent context, burns rate budget, and forces SQL fallbacks for compact discovery.
Describe the solution you'd like
Extend Tickets.Tickets.getAll searchCriteria (and MCP list-ticket tools) with first-class server-side filters:
modifiedAfter (ISO datetime) — keep tickets whose modified (fallback date) is on/after that instant- Documented
status / statusType filters that work without requiring a project id when the caller is authorized across projects (admin / assigned projects)
Ideal response shape for agents: still full ticket objects when needed, but filtering happens on the server so clients do not download the whole workspace.
Additional context
Related prior discussion: statusType search (#2533). We are happy with either core JSON-RPC or MCP-layer wrappers as long as the filter is server-side. Happy to validate a PR against our agent checkpoint runners.
What is your set up?
Self Hosted Docker (Kubernetes)
Is your feature request related to a problem? Please describe
We run self-hosted Leantime as the system of record for a small multi-agent PM workflow (Cursor agents coordinating tickets, checkpoints, and handoffs via JSON-RPC / MCP). Watcher jobs need “only tickets updated since T” and “only In Progress / statusType=INPROGRESS”, but
Tickets.getAllhas no reliablemodifiedAfter, so clients must pull large payloads and filter locally. That floods agent context, burns rate budget, and forces SQL fallbacks for compact discovery.Describe the solution you'd like
Extend
Tickets.Tickets.getAllsearchCriteria(and MCP list-ticket tools) with first-class server-side filters:modifiedAfter(ISO datetime) — keep tickets whosemodified(fallbackdate) is on/after that instantstatus/statusTypefilters that work without requiring a project id when the caller is authorized across projects (admin / assigned projects)Ideal response shape for agents: still full ticket objects when needed, but filtering happens on the server so clients do not download the whole workspace.
Additional context
Related prior discussion: statusType search (#2533). We are happy with either core JSON-RPC or MCP-layer wrappers as long as the filter is server-side. Happy to validate a PR against our agent checkpoint runners.