Elixion

Projects Overview

Learn how projects work in Elixion and how to organize your work effectively

Projects Overview

Projects are the fundamental organizational unit in Elixion. They contain all the issues, sprints, and documentation related to a specific initiative, product, or team effort.

What is a Project?

A project in Elixion is a container that holds:

  • Issues - Tasks, bugs, stories, and epics
  • Sprints - Time-boxed iterations for agile teams
  • Board - Kanban visualization of work
  • Timeline - Gantt-style planning view
  • Documents - Related documentation and knowledge base
  • Team - Project members and their roles
  • Settings - Project-specific configuration

Project Structure

Project
├── Issues
│   ├── Epics
│   │   └── Stories
│   │       └── Tasks
│   ├── Bugs
│   └── Tech Debt
├── Sprints
│   ├── Active Sprint
│   └── Backlog
├── Board
├── Timeline
├── Documents
└── Settings

Key Concepts

Project Key

Every project has a unique key (e.g., PROJ, CORE, UI) used to prefix issue identifiers:

PROJ-123  // Issue 123 in project with key "PROJ"
CORE-456  // Issue 456 in project with key "CORE"

Project Status

Projects can have the following statuses:

| Status | Description | |--------|-------------| | Active | Currently being worked on | | On Hold | Temporarily paused | | Completed | All work finished | | Archived | No longer active, kept for reference |

Project Access

Elixion has no project visibility setting (no Public/Private/Restricted modes). Access is determined entirely by project membership: if you're added as a project member, you can see it; if not, you can't. See Permissions for how this actually works, and the note there about the planned org boundary (ELI-1284).

Project Dashboard

When you open a project, you'll see the dashboard with:

Overview Section

  • Project description and key information
  • Quick stats (open issues, completion rate)
  • Recent activity feed

Progress Metrics

  • Sprint burndown/burnup
  • Issue status distribution
  • Velocity trends

Team Activity

  • Recent comments and updates
  • Active team members
  • Assignment distribution

Accessing Projects

From the Sidebar

Click Projects in the sidebar to see all projects you have access to.

From Spaces

Projects can be organized into Spaces. Select a space to filter projects.

From Search

Use quick search (Ctrl/Cmd + K) to find projects by name or key.

From Favorites

Star frequently accessed projects to add them to your Favorites.

Project Views

List View

See all projects in a table format with:

  • Project name and key
  • Owner/Lead
  • Status
  • Issue counts
  • Last activity

Card View

Visual cards showing project previews with key metrics.

Hierarchy View

See project relationships and groupings within spaces.

Project Permissions

Projects have role-based access control via project membership. See Permissions for the actual role model (OWNER/ADMIN/VIEWER plus job-function roles like DEVELOPER) — the "Manager" role referenced elsewhere in older docs does not exist.

Best Practices

Naming Conventions

  • Use clear, descriptive names
  • Include team or product identifier if helpful
  • Keep names concise but informative

Good examples:

  • "User Authentication Service"
  • "Mobile App - iOS"
  • "Q1 Marketing Campaign"

Avoid:

  • "Project 1"
  • "misc"
  • "stuff to do"

Project Keys

  • Keep keys short (2-5 characters)
  • Use memorable abbreviations
  • Make them unique across the organization

Organization

  • Use Spaces to group related projects
  • Archive completed projects instead of deleting
  • Maintain active project documentation

Team Setup

  • Assign a clear project lead
  • Define roles upfront
  • Keep team size manageable (7-10 people max)

Related Features

Next: Creating Projects - Learn how to create and set up a new project