Skip to content

Projects

Projects are the top-level containers in DevFlow. Every Flow, release, time entry, and team assignment lives inside a project. Whether you are building a single product or managing several, each project gives you a dedicated workspace with its own Kanban board, dashboard, and settings.

  1. Click “New Project” in the sidebar or on the Dashboard
  2. Enter a project name
  3. Optionally add a description, logo, and color
  4. Click Create

Your project appears in the sidebar immediately. You are redirected to the project settings page where you can configure details.

Open settings via the gear icon on the project page. Settings are organized into five tabs.

  • Project Name and Description — Identify your project. Changes save automatically as you type.
  • Flow Prefix — A 2-5 character code used for Flow IDs. For example, if the prefix is MA, Flows are numbered MA-1, MA-2, and so on. DevFlow auto-suggests a prefix based on the project name.
  • Color — Pick a color to visually distinguish this project in the sidebar, timer, and time tracking views.
  • Logo — Upload an image (PNG, JPG, or SVG, max 500 KB) or paste an image URL. The logo appears in the sidebar and on project cards.
  • Auto Timer — When enabled, the timer automatically starts and switches context when you begin working on Flows in this project.
  • Tracking Level — Choose what granularity time is tracked at: Project, Flow, or Ticket.
  • Takt (Rounding) — Set a project-specific rounding interval for time blocks (5, 15, 30, or 60 minutes). Leave empty to use your global default.
  • Transfer Project — Owners can move a project between their personal space and an organization.
  • Delete Project — Permanently removes the project. Only available to the project owner.

If your project belongs to an organization, the Team tab shows all members and their roles. You can manage who has access and what permissions they hold.

For personal projects (outside an organization), you are the only member.

Store project-specific documentation, architecture notes, tech stack details, and agent instructions. This information is available to AI agents working on the project, helping them understand your codebase and conventions.

Configure how AI agents interact with Git in this project. Rules are set up through a step-by-step wizard that covers:

  • Default branch — Usually main or master
  • Branch naming — How Flow branches should be named (e.g., feature/MA-1-add-login)
  • Commit conventions — Commit message format (e.g., conventional commits)
  • PR templates — How pull request descriptions should be structured
  • Automations — Auto-create PRs when Flows are completed, auto-assign Flows to the active release

A live preview shows how the generated guidelines will look.

Connect external tools to your project. Integrations (GitHub, GitLab, Slack) are planned for future releases.

Each project has a dedicated dashboard that gives you an overview of the current state:

  • Flow Pipeline — A visual summary of how many Flows are in each state (idea, planning, approval, ready, in progress, review, done)
  • Recent Activity — The latest Flow updates, state transitions, and team actions
  • Release Progress — Status of the current active release, including how many Flows are completed vs. remaining
  • Time Statistics — Hours tracked per week and month, broken down by project member

Projects support three roles with different access levels:

RoleCapabilities
OwnerFull control. Can edit all settings, transfer or delete the project, manage members and roles
ManagerCan edit project settings, manage Flows, and manage team members
MemberCan view the project, create and work on Flows, and track time

In organization-owned projects, roles are inherited from the organization membership but can be adjusted at the project level.