HN Showcase
Back to browse
FirstDraft – AI workers that claim Jira tickets and open PRs

FirstDraft – AI workers that claim Jira tickets and open PRs

by gamerdrome·Jun 4, 2026·2 points·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidShip ItSolve My Problem

Jira-first AI workflow when Cursor and Devin start from chat prompts instead.

Strengths
  • •Ticket locking prevents multiple workers from claiming the same Jira issue
  • •Runs locally with your existing repos, credentials, and build tools
  • •Draft PR output keeps humans in the review loop by design
Weaknesses
  • •No novel AI architecture—orchestrates Claude Code and Codex without differentiation
  • •Jira-only integration excludes teams using Linear, GitHub Issues, or other trackers
Category
AI/ML
Target Audience

Engineering teams using Jira who want to automate small bug fixes and features

Similar To

Cursor · Devin · Continue

Post Description

I’ve been spending a lot of time with Codex at work like many people, and found myself doing the same thing over and over:

- Pick a Jira ticket - Start an agent - Explain the task - Wait for it to finish - Open a PR - Repeat

So I built FirstDraft.

A worker runs on a machine that already has access to your repositories, build tools, credentials, and anything else it needs. It watches a Jira board, claims a ticket, runs Claude Code or Codex locally, pushes a branch, and opens a draft PR.

The goal was to push through some of those smaller bug tickets and features that could be done without me having to pick them up myself.

What’s been interesting is that once I got the basics working, I started using FirstDraft to build FirstDraft. A lot of the features in the current version were implemented by workers picking up Jira tickets and opening PRs.

It’s still early and very much an experiment, but it’s been a fun one.

Similar Projects