Skip to content

Project Management

Jump to bottom
Jack Pickett edited this page Feb 6, 2025 · 2 revisions

Project Management

This document describes how projects are managed in the Geneva system.

Project Boards

Each project in Geneva has its own project board that tracks issues and their status. Project boards provide:

  • Visual task organization
  • Status tracking
  • Progress monitoring
  • Team coordination

Current Projects

  1. The Paddock (Project #1)

Managing Issues

Viewing Project Data

# Get project board data
GET /api/github/projects/:projectNumber/board

# List all projects
GET /api/github/projects

# Get project fields
GET /api/github/projects/:projectId/fields

Adding Issues to Projects

POST /api/github/issues/:issueNumber/project/:projectNumber

Example:

# Add issue #15 to Paddock (Project #1)
POST /api/github/issues/15/project/1

When an issue is added to a project:

  1. Issue appears on the project board
  2. Status is automatically set to "Todo"
  3. Progress can be tracked through status updates

Status Updates

POST /api/github/issues/:issueNumber/status
{
  "status": "todo|inProgress|inReview|done",
  "projectNumber": 1
}

Status Workflow

Issues move through a standard workflow:

  1. Todo

    • Newly added issues
    • Issues ready to be worked on
    POST /api/github/issues/:issueNumber/status
{
  "status": "todo",
  "projectNumber": 1
}

  2. In Progress

    • Currently being worked on
    • Assigned to specific agent
    POST /api/github/issues/:issueNumber/status
{
  "status": "inProgress",
  "projectNumber": 1
}

  3. In Review

    • Work completed
    • Awaiting review/approval
    POST /api/github/issues/:issueNumber/status
{
  "status": "inReview",
  "projectNumber": 1
}

  4. Done

    • Work approved
    • Issue resolved
    POST /api/github/issues/:issueNumber/status
{
  "status": "done",
  "projectNumber": 1
}

Project Numbers

Project numbers are unique identifiers for each project board:

Number Project Description
1 Paddock Main development board for Horse agents

Best Practices

  1. Issue Organization

    • Add issues to relevant project immediately
    • Keep status up to date using API endpoints
    • Link related issues using #number references
    • Include project number in issue creation

  2. Project Board Usage

    • Review board data regularly via API
    • Update status as work progresses
    • Use issue comments for status context
    • Monitor project fields for changes

  3. API Usage

    • Include agent ID header in all requests
    • Handle rate limits appropriately
    • Validate input before sending
    • Check response status codes
    • Use consistent status values

Clone this wiki locally