Alpha Projects
Organize agile work under projects with dedicated backlogs, sprints, and team assignments
Agile Projects
Projects are the top-level container for all agile work. Each project has its own backlog, sprints, board, and team members. Use projects to separate work by product, team, or initiative.
Creating a Project
To create a new project:
- Navigate to Tasks > Projects
- Click New Project
- Fill in the project details:
- Name -- a clear, recognizable project name
- Key -- a short prefix used for task IDs (e.g.,
ALPHA,WEB) - Description -- what this project covers
- Click Save
Project Structure
Each project contains:
| Component | Description |
|---|---|
| Backlog | All unscheduled tasks and stories for the project |
| Sprints | Time-boxed iterations planned from the backlog |
| Board | Kanban view of the active sprint |
| Epics | Large initiatives that span multiple sprints |
| Features | Deliverable chunks of work within epics |
| Releases | Planned releases grouping completed features |
Linking Epics and Features
Projects connect to epics and features to provide high-level planning:
- An epic belongs to a project and represents a major initiative
- A feature belongs to an epic and breaks it into shippable pieces
- Tasks belong to features and represent the actual work
This hierarchy allows you to track progress from individual tasks up through features and epics to the project level.
Team Members
Assign team members to a project to control who can be assigned tasks and who appears in project filters. Team members see the project in their dashboard and receive notifications for relevant updates.
Project Visibility (Public & Private)
Every project has a visibility setting that controls who can see it and its contents (board, tasks, sprints, epics).
| Visibility | Who can see it |
|---|---|
| Public (default) | Anyone in the tenant with the Read projects permission |
| Private | Only explicitly-added members, the project's creator, and administrators (super-admins / full-access users) |
Making a project private
- When creating a project, switch on Private project in the create dialog.
- For an existing project, open Project > Settings, toggle Private project, and click Save changes.
When a project is private, a lock badge appears next to its name.
Managing who has access
On a private project's Settings page, click Manage access to add or remove members. Notes:
- The creator is added automatically and always retains access.
- Administrators (super-admins and full-access users) always have access and don't need to be added.
- Removing a member immediately hides the project, its board, and all of its tasks/sprints/epics from them.
Private projects are hidden from project lists, return Access denied on direct links, and their board data is blocked for non-members — so private really means private, not just "hidden from the list".