[feature]: Promote Cycles to the Workspace level rather than Project level

Is there an existing issue for this?

• I have searched the existing issues

Summary

Cycles are intended to manage tasking in a manner similar to Agile "sprints". As such, a matrixed development team may be assigned to work on multiple issues from multiple projects. The current implementation requires a Scrum master or project manager to move between multiple projects to get an individual's status on their tasking.

This process is frustrating and a shortcoming for Plane.

Fortunately, it can be remedied. If Cycles were promoted to the Workspace level, a project manager could assign issues to a Cycle from any project in the Workspace. The project manager would also be able to use a single Agile board to move tasking through the workflow.

Why should this be worked on?

The current implementation for Cycles requires project managers to navigate multiple projects to get status updates on issues. It's time consuming and frustrating for teams that leverage Agile methodologies.

Start by tracing how Cycles are currently scoped to projects and how workspace issues and Agile boards are represented. The issue provides no file or test entry points, so first map those boundaries before proposing changes. Done means a Cycle can include issues from multiple projects and a project manager can manage them from one workspace-level board.