Project Management Integration

DevDaily can extract ticket IDs from branch names and commit messages, then fetch metadata from your project management tool to enrich standups, PR descriptions, and work summaries.

Supported Tools

GitHub Issues

Uses gh CLI (no additional auth required)

Jira

REST API v3 with email + API token

Linear

GraphQL API with API key

Notion

REST API with integration token

Quick Setup

Run the interactive setup wizard:

devdaily connect

Or specify a tool directly:

devdaily connect --tool github
devdaily connect --tool jira
devdaily connect --tool linear
devdaily connect --tool notion

Configuration

Set your project management tool in .devdaily.json:

.devdaily.json

{
  "projectManagement": {
    "tool": "github",
    "ticketPrefix": "PROJ",
    "ticketPattern": null,
    
    "jira": {
      "baseUrl": "https://yourcompany.atlassian.net",
      "useApiToken": true,
      "projectKey": "PROJ"
    },
    
    "linear": {
      "teamKey": "ENG",
      "useApi": true
    },
    
    "notion": {
      "databaseId": "your-database-id",
      "useApi": true
    }
  }
}

enum

default:"github"

Primary project management tool: github, jira, linear, notion, or none

string

Ticket ID prefix (e.g., PROJ, ENG, DEV). Used to extract ticket numbers from branch names and commits.

string (regex)

Custom regex pattern for ticket extraction (advanced). Overrides default patterns.

GitHub Issues

Authentication

GitHub Issues uses the gh CLI, which must be authenticated:

gh auth login
gh auth status

No additional configuration needed - DevDaily reuses your gh session.

Configuration

.devdaily.json

{
  "projectManagement": {
    "tool": "github"
  }
}

Ticket ID Patterns

GitHub Issues are referenced by number:

#123 - Issue number 123
gh-123 - Alternative format

Extracted from:

Branch names: feature/123-auth-refactor, fix/#456-bug
Commit messages: Fix #123: Add authentication

Example

# Create a branch referencing issue #123
git checkout -b feature/123-auth-refactor

# DevDaily will automatically fetch issue details
devdaily standup
# Output includes:
# [#123] Add OAuth2 authentication
#   Type: feature | Status: open
#   Implement OAuth2 flow with GitHub provider

Jira

Authentication

Jira requires:

Base URL: Your Jira instance URL
Email: Your Jira account email
API Token: Generate at https://id.atlassian.com/manage-profile/security/api-tokens

Generate API Token

Go to https://id.atlassian.com/manage-profile/security/api-tokens
Click “Create API token”
Name it “DevDaily” and copy the token

Store Credentials

Add to ~/.config/devdaily/secrets.json:

{
  "jira": {
    "baseUrl": "https://yourcompany.atlassian.net",
    "email": "your@email.com",
    "apiToken": "your-api-token-here"
  }
}

Configure Tool

Set in .devdaily.json:

{
  "projectManagement": {
    "tool": "jira",
    "ticketPrefix": "PROJ",
    "jira": {
      "projectKey": "PROJ",
      "useApiToken": true
    }
  }
}

Test Connection

devdaily connect --test

Configuration

string

required

Jira instance URL (e.g., https://yourcompany.atlassian.net)

string

Default project key for searches (e.g., PROJ, ENG)

boolean

default:"true"

Use API token authentication (recommended)

Ticket ID Patterns

Jira tickets follow the format PROJECT-123:

PROJ-123 - Standard format
ENG-456 - Different project

Extracted from:

Branch names: feature/PROJ-123-auth, PROJ-456/implementation
Commit messages: PROJ-123: Add authentication

Environment Variables

export JIRA_BASE_URL="https://yourcompany.atlassian.net"
export JIRA_EMAIL="your@email.com"
export JIRA_API_TOKEN="your-token"

Example

git checkout -b feature/PROJ-123-oauth

devdaily pr --create
# Output includes:
# **Ticket No:** PROJ-123
# **Ticket link:** https://yourcompany.atlassian.net/browse/PROJ-123
# **Summary:** Implement OAuth2 authentication
# **Status:** In Progress

Linear

Authentication

Linear requires an API key:

Generate API Key

Go to https://linear.app/settings/api
Click “Create new API key”
Name it “DevDaily” and copy the key

Store API Key

Add to ~/.config/devdaily/secrets.json:

{
  "linear": {
    "apiKey": "lin_api_..."
  }
}

Configure Tool

.devdaily.json

{
  "projectManagement": {
    "tool": "linear",
    "ticketPrefix": "ENG",
    "linear": {
      "teamKey": "ENG",
      "useApi": true
    }
  }
}

Configuration

string

Team identifier (e.g., ENG, DEV, PROD)

boolean

default:"true"

Use Linear API (vs CLI - API recommended)

Ticket ID Patterns

Linear tickets use format TEAM-123:

ENG-123 - Engineering team issue
DEV-456 - Development team issue

Extracted from:

Branch names: feature/ENG-123-auth, ENG-456/bugfix
Commit messages: ENG-123: Implement OAuth

Environment Variables

export LINEAR_API_KEY="lin_api_..."

Example

git checkout -b feature/ENG-123-oauth

devdaily standup
# Output includes:
# [ENG-123] Implement OAuth2 authentication
#   Type: feature | Status: In Progress | Priority: high
#   Add OAuth2 flow with Google provider

Notion

Authentication

Notion requires:

Integration Token: Create an integration at https://www.notion.so/my-integrations
Database ID: The ID of your tasks/issues database

Create Integration

Go to https://www.notion.so/my-integrations
Click “New integration”
Name it “DevDaily” and save
Copy the “Internal Integration Token”

Share Database

Open your tasks/issues database in Notion
Click ”…” → “Add connections”
Select your “DevDaily” integration

Get Database ID

From the database URL:

https://notion.so/yourworkspace/DATABASE_ID?v=...
                                 ^^^^^^^^^^^^

Store Credentials

~/.config/devdaily/secrets.json

{
  "notion": {
    "apiKey": "secret_...",
    "databaseId": "your-database-id"
  }
}

Configuration

string

required

Notion database ID containing tasks/issues

boolean

default:"true"

Use Notion API (recommended)

Ticket ID Patterns

Notion uses UUIDs:

a1b2c3d4-e5f6-7890-abcd-ef1234567890 - Full UUID
a1b2c3d4e5f67890abcdef1234567890 - UUID without hyphens

Notion integration is limited compared to other tools because Notion doesn’t have built-in issue tracking. Best used with structured databases.

Environment Variables

export NOTION_API_KEY="secret_..."
export NOTION_DATABASE_ID="your-database-id"

Ticket Extraction

DevDaily automatically extracts ticket IDs from:

Branch Names

Common patterns:

# Standard formats
feature/PROJ-123-description
fix/PROJ-456-bugfix
bugfix/PROJ-789

# Prefixed formats
user/PROJ-123-feature
team/ENG-456-implementation

# Just the ticket
PROJ-123/description
PROJ-123-feature-name

# Numeric only (with ticketPrefix config)
feature/123-description  # Becomes PROJ-123

Commit Messages

# Reference in title
git commit -m "PROJ-123: Add authentication"
git commit -m "Fix #456: Resolve login bug"

# Reference in body
git commit -m "Add OAuth" -m "Implements PROJ-123"

# Multiple tickets
git commit -m "PROJ-123 PROJ-124: Refactor auth"

Custom Patterns

For non-standard formats, use a custom regex:

.devdaily.json

{
  "projectManagement": {
    "ticketPattern": "\\b(CUSTOM-\\d+)\\b"
  }
}

Fetched Metadata

DevDaily fetches the following ticket data:

string

Ticket ID (e.g., PROJ-123, #456, ENG-789)

string

Ticket title/summary

string

Full ticket description

string

Current status (e.g., In Progress, Done, open)

enum

Issue type: bug, feature, task, story, epic, or other

enum

Priority level: low, medium, high, or critical

string

Assigned person’s name

string[]

Associated labels/tags

string

Direct link to ticket

Testing Connection

Verify your PM integration is working:

# Test connection and auth
devdaily connect --test

# Output:
# ✓ GitHub: Authenticated as username (repo: owner/repo)
# ✓ Connection successful (120ms)

# Fetch a specific ticket
devdaily standup --ticket PROJ-123 --debug

Usage in Commands

Standup

Tickets are automatically included in standups:

devdaily standup

# Output includes ticket metadata:
# Yesterday:
# - [PROJ-123] Implement OAuth2 authentication
#   → Added Google OAuth provider
#   → Updated user model
#   📎 https://yourcompany.atlassian.net/browse/PROJ-123

PR Descriptions

Ticket data enriches PR descriptions:

devdaily pr --create

# PR body includes:
# ## Ticket
# **Ticket No:** PROJ-123
# **Ticket link:** https://yourcompany.atlassian.net/browse/PROJ-123
# **Summary:** Implement OAuth2 authentication

Weekly Summaries

devdaily week

# Groups work by ticket:
# This Week:
# 
# PROJ-123: Implement OAuth2 authentication
# - Added Google OAuth provider
# - Updated user model
# - Fixed token refresh bug

Disabling PM Integration

To disable project management integration:

.devdaily.json

{
  "projectManagement": {
    "tool": "none"
  }
}

DevDaily will still extract ticket IDs from branch names but won’t fetch metadata.

Troubleshooting

Authentication Errors

Jira: 401 Unauthorized

Verify email and API token in secrets.json
Check token hasn’t expired
Ensure baseUrl is correct (no trailing slash)
Test: curl -u email:token https://yourcompany.atlassian.net/rest/api/3/myself

Linear: Invalid API Key

Verify API key in secrets.json starts with lin_api_
Regenerate at https://linear.app/settings/api
Check key has required permissions

GitHub: Not authenticated

Run gh auth login
Verify: gh auth status
Ensure gh CLI version >= 2.0

Notion: 404 Not Found

Verify database ID is correct
Check integration has access to database
Re-share database with integration

Tickets Not Found

Check ticket ID format:

devdaily standup --debug
# Shows extracted ticket IDs

Verify ticketPrefix:

{
  "projectManagement": {
    "ticketPrefix": "PROJ"  // Must match your tickets
  }
}

Test extraction manually:

echo "feature/PROJ-123-auth" | grep -oE '[A-Z]+-[0-9]+'

Rate Limiting

API rate limits:

Jira: 10 req/sec per user
Linear: 2000 req/hour
GitHub: 5000 req/hour (authenticated)

DevDaily caches ticket data during command execution to minimize API calls.

Best Practices

Use consistent branch naming

Always include ticket ID in branch names:

git checkout -b feature/PROJ-123-description

Reference tickets in commits

git commit -m "PROJ-123: Add OAuth provider"

Configure ticketPrefix

Set your team’s standard prefix:

{ "projectManagement": { "ticketPrefix": "PROJ" } }

Test before relying on automation

devdaily connect --test
devdaily standup --ticket PROJ-123 --debug

Configuration Overview

Learn about all configuration options

PR Templates

Customize how ticket data appears in PRs

​Supported Tools

GitHub Issues

Jira

Linear

Notion

​Quick Setup

​Configuration

​GitHub Issues

​Authentication

​Configuration

​Ticket ID Patterns

​Example

​Jira

​Authentication

​Configuration

​Ticket ID Patterns

​Environment Variables

​Example

​Linear

​Authentication

​Configuration

​Ticket ID Patterns

​Environment Variables

​Example

​Notion

​Authentication

​Configuration

​Ticket ID Patterns

​Environment Variables

​Ticket Extraction

​Branch Names

​Commit Messages

​Custom Patterns

​Fetched Metadata

​Testing Connection

​Usage in Commands

​Standup

​PR Descriptions

​Weekly Summaries

​Disabling PM Integration

​Troubleshooting

​Authentication Errors

​Tickets Not Found

​Rate Limiting

​Best Practices

​Related Configuration

Configuration Overview

PR Templates

Supported Tools

Quick Setup

Configuration

GitHub Issues

Authentication

Configuration

Ticket ID Patterns

Example

Jira

Authentication

Configuration

Ticket ID Patterns

Environment Variables

Example

Linear

Authentication

Configuration

Ticket ID Patterns

Environment Variables

Example

Notion

Authentication

Configuration

Ticket ID Patterns

Environment Variables

Ticket Extraction

Branch Names

Commit Messages

Custom Patterns

Fetched Metadata

Testing Connection

Usage in Commands

Standup

PR Descriptions

Weekly Summaries

Disabling PM Integration

Troubleshooting

Authentication Errors

Tickets Not Found

Rate Limiting

Best Practices

Related Configuration