GitHub Issues and Projects: Agile Management

Title: [Bug] Login form submits with empty email on Safari 17
(Prefix with type, be specific about the symptom)

Description:
**Behaviour**: Clicking Submit with an empty email field does not show a
validation error on Safari 17.0. The form submits and returns a 422 from the API.

**Expected**: The browser-native validation should prevent submission.

**Steps to reproduce**:
1. Open the login page on Safari 17.0 macOS Ventura
2. Leave the email field empty
3. Enter any password
4. Click Submit

**Environment**:
- Browser: Safari 17.0
- OS: macOS 14.1
- App version: 2.4.1

**Additional context**: Works correctly on Chrome 124 and Firefox 125.

Type labels:
  bug          — Something is broken
  enhancement  — New feature or improvement
  question     — Discussion or help request
  chore        — Non-user-facing maintenance

Priority labels:
  priority: critical   — Blocks users from core functionality
  priority: high       — Degrades user experience significantly
  priority: medium     — Normal priority
  priority: low        — Nice to have

Status labels:
  status: blocked      — Cannot progress without external dependency
  status: needs-info   — Waiting for more information from reporter
  status: in-progress  — Being actively worked on

Audience labels:
  good first issue     — Low complexity, good for new contributors
  help wanted          — Open for community contributions

# Create labels via GitHub CLI
gh label create "priority: critical" --color "D93F0B" --description "Blocks users from core functionality"
gh label create "priority: high" --color "E4E669" --description "Significant UX degradation"
gh label create "good first issue" --color "7057FF" --description "Good for newcomers"

# .github/ISSUE_TEMPLATE/bug_report.yml
name: Bug Report
description: Report a bug or unexpected behaviour
labels: ["bug", "status: needs-info"]
assignees: []

body:
  - type: markdown
    attributes:
      value: "Thanks for reporting a bug. Please fill in all sections."

  - type: textarea
    id: description
    attributes:
      label: What happened?
      description: A clear description of the bug
    validations:
      required: true

  - type: textarea
    id: steps
    attributes:
      label: Steps to reproduce
      placeholder: |
        1. Go to...
        2. Click on...
        3. See error
    validations:
      required: true

  - type: textarea
    id: expected
    attributes:
      label: Expected behaviour
    validations:
      required: true

  - type: dropdown
    id: severity
    attributes:
      label: Severity
      options:
        - Critical (blocks all users)
        - High (blocks some users)
        - Medium (workaround exists)
        - Low (cosmetic only)
    validations:
      required: true

  - type: input
    id: version
    attributes:
      label: App version
      placeholder: "2.4.1"
    validations:
      required: true

# .github/ISSUE_TEMPLATE/feature_request.yml
name: Feature Request
description: Propose a new feature or enhancement
labels: ["enhancement"]

body:
  - type: textarea
    id: problem
    attributes:
      label: What problem does this solve?
      description: Describe the user problem, not the solution
    validations:
      required: true

  - type: textarea
    id: solution
    attributes:
      label: Proposed solution
    validations:
      required: true

  - type: textarea
    id: alternatives
    attributes:
      label: Alternatives considered
      description: What other solutions did you consider?

# Via GitHub CLI
gh api repos/my-org/my-repo/milestones \
  --method POST \
  --field title="v2.5.0" \
  --field description="Payment redesign and mobile performance improvements" \
  --field due_on="2026-06-01T00:00:00Z"

Sprint 23 (2026-05-05 → 2026-05-16)
├── Bug: Login Safari validation (3 points)
├── Feature: Dark mode toggle (5 points)
├── Chore: Upgrade Node.js to 22 (2 points)
├── Bug: PDF export encoding (2 points)
└── Feature: Export to CSV (8 points)
                    Progress: 7/20 points (35%)

Field name: Story Points     Type: Number
Field name: Team             Type: Single select (Frontend, Backend, Platform, QA)
Field name: Quarter          Type: Single select (Q1, Q2, Q3, Q4)
Field name: Start Date       Type: Date
Field name: Due Date         Type: Date

# .github/workflows/project-automation.yml
name: Project Automation

on:
  pull_request:
    types: [opened, converted_to_draft, ready_for_review]

jobs:
  update-project:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/github-script@v7
        with:
          github-token: ${{ secrets.PROJECT_AUTOMATION_TOKEN }}
          script: |
            const prNumber = context.payload.pull_request.number;
            const status = context.payload.action === 'opened' ||
                           context.payload.action === 'ready_for_review'
                           ? 'In Review'
                           : 'In Progress';

            // Find linked issues and update their project status
            const linkedIssues = await github.rest.issues.listEventsForTimeline({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: prNumber
            });

            console.log(`Setting status "${status}" for PR #${prNumber}`);

# In a PR description or commit message
Fixes #123
Closes #456
Resolves #789

# Multiple issues
Closes #123, closes #456

# List open bugs assigned to the current user
gh issue list --label bug --assignee @me --state open

# List all critical issues across the organisation
gh issue list \
  --repo my-org/api-service \
  --label "priority: critical" \
  --json number,title,assignees,createdAt

# Find issues not updated in 30+ days (stale issues)
gh issue list \
  --state open \
  --json number,title,updatedAt \
  | jq '[.[] | select(.updatedAt < (now - 2592000 | todate))]'

# Create an issue from a template
gh issue create \
  --title "API returns 500 on /users endpoint" \
  --body-file ./templates/bug-report.md \
  --label "bug,priority: high" \
  --assignee alice

Sprint Planning (Monday morning):
1. Create milestone "Sprint 24" with end date
2. Review backlog issues, assign points via custom field
3. Add selected issues to the sprint milestone
4. Assign each issue to a developer
5. Set all sprint issues to "Todo" status in project

During Sprint:
- Developer picks an issue → moves to "In Progress"
- Developer opens a PR linking the issue → moves to "In Review"
- PR is reviewed and merged → issue automatically closes and moves to "Done"

Sprint Review (Friday afternoon):
- Filter project by milestone = Sprint 24
- Velocity: count closed story points
- Carryover: move unclosed issues to Sprint 25 milestone

Retrospective actions:
- "Blocked" items → create chore issues for removing blockers
- Recurring bug type → create label and template for it

# .github/ISSUE_TEMPLATE/config.yml
blank_issues_enabled: false
contact_links:
  - name: Security vulnerability
    url: https://github.com/my-org/my-repo/security/advisories/new
    about: Report a security issue privately
  - name: Ask a question
    url: https://github.com/my-org/my-repo/discussions
    about: Use Discussions for questions

# .github/workflows/recurring-issues.yml
on:
  schedule:
    - cron: '0 9 * * 1'   # Every Monday at 9am

jobs:
  create-sprint-issue:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/github-script@v7
        with:
          script: |
            await github.rest.issues.create({
              owner: context.repo.owner,
              repo: context.repo.repo,
              title: `Weekly deployment checklist — ${new Date().toISOString().slice(0, 10)}`,
              labels: ['chore'],
              body: '- [ ] Check Dependabot alerts\n- [ ] Review error rates\n- [ ] Deploy to staging\n- [ ] Smoke test\n- [ ] Deploy to production'
            });