Add "Active Cycle" filter to "Your Work" page for cross-project visibility

[mattgle]

Summary

It would be great to have an "Active Cycle" filter (or a dedicated view) on the Your Work page that shows all tickets assigned to you that belong to an active cycle, across all projects in the workspace.

Problem

Currently, there's no easy way to see all your assigned work items that are part of an active cycle across multiple projects. The workarounds are:

• Your Work page — Shows all assigned items but has no cycle filter
• Workspace Views — Support cycle filtering, but cycles are project-scoped, so you have to manually select each project's active cycle and update the view every time cycles roll over
• Per-project Cycle views — Filter by assignee within a single project's cycle, but don't aggregate across projects

Proposed Solution

Add a filter option to the "Your Work" page (or Workspace Views) for "Active Cycle" that automatically includes work items belonging to whichever cycle is currently active in each project. This would eliminate the need to manually select and update individual cycle filters.

Use Case

As someone working across multiple projects, I want a single view that answers: "What's on my plate for the current sprint/cycle across everything?" without manually maintaining filters each time cycles change.

[pushya22]

Hi @mattgle we do have plans to add cycles and modules to at workspace level layouts.

[mattgle]

Hi @mattgle we do have plans to add cycles and modules to at workspace level layouts.

Nice, any ETA for that? Thanks for replying btw :)

[wang2-lat]

这个需求很合理。可以考虑在 Your Work 页面加一个 cycle 状态筛选器（类似 Workspace Views 的实现），或者直接复用现有的 cycle filter 逻辑来快速支持跨项目的 active cycle 视图。

[Vansh5632]

Hi @pushya22, I explored this issue and went through the codebase, and I have an implementation plan for it.

Currently, our setup is UUID-dependent. The frontend resolves a specific cycle ID and passes it as ?cycle=<uuid> directly to the API, but this becomes slow when dealing with a large number of projects.

To support the "Active Cycle" filter, we should shift cycle resolution from the client to the server by introducing a reserved "current" token.

We can implement this by intercepting "current" as a valid value for the cycle parameter. Instead of performing a UUID lookup, we would inject a dynamic ORM date-range subquery.

This would resolve active cycles across all projects in a single database query.

Your views and suggestions would be appreciated. If you’re okay with this approach, I can raise a PR soon.