Add "Active Cycle" filter to "Your Work" page for cross-project visibility
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the Your Work page, Workspace Views, and per-project Cycle views described in the issue to determine where cross-project active-cycle filtering belongs. Define completion as one view showing each assigned item from the currently active cycle in every project without manual cycle updates; the issue names no implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100