Agents In Use
What’s new todayLast update
3 use cases added today

How Claude Code helped prepare Jira tickets for coding agents

u/Hefty_Professor_4170 built a Claude Code workflow across more than 30 Git repositories. Two people used separate Claude sessions to review and revise Jira tickets before handing them to coding agents.

OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Review these Jira tickets for missing technical requirements and acceptance criteria. Ask the reporter specific questions instead of inventing answers. Propose revisions for human approval. Keep unresolved decisions explicit before handing any ticket to an implementation agent.

Evidence at a glance

Sourced account
Source poster / publisher
u/Hefty_Professor_4170
Original account
Read the source ↗
Published
Source link checked
Reported result
The author reports a working ticket-to-implementation setup and a specific exchange where Claude reviewed requirements while a colleague used another Claude session to update the tickets. No completed feature, test result or measured productivity gain is documented.
Human involvement
The adviser and colleague supplied requirements and passed feedback between sessions. The author says people can redirect agents, provide feedback or reject their actions.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. The adviser configured a Claude Code fleet with repository access, a custom plugin and task-specific skills.
  2. Tagged Jira tickets gave agents work to clarify with the reporter before implementation.
  3. The adviser asked a separate Claude session to review a colleague's incomplete feature tickets.

Jira tickets need enough detail for a coding agent to act without inventing requirements. Reddit user u/Hefty_Professor_4170 describes using Claude Code to prepare that handoff at a company they advise. Their setup gives a fleet of agents access to more than 30 Git repositories, with a custom plugin and skills defining how work should proceed.

The author says agents pick up tagged tickets, clarify technical requirements and acceptance criteria with the reporter, then start implementing. One colleague, primarily a QA specialist, wanted a new feature but had not prepared tickets that were ready for the fleet. The adviser asked a separate Claude Code session to review them.

The colleague was also using Claude Code to respond to the feedback and update Jira. Two humans were therefore passing messages between two Claude sessions so a separate set of agents could later implement the work. The observed example is the requirements exchange, not proof that this particular feature shipped.

In a returned comment, the author says people can interact directly with agents, redirect them or reject actions. Each agent has a defined goal and context. This is a supervised coordination workflow, not evidence of independent agents negotiating company priorities. The account includes no code artifact, test results or measured time saving. Its practical lesson is to separate ticket clarification from implementation and keep unresolved decisions visible to people.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Reddit · u/Hefty_Professor_4170

Frequently asked questions

Did the agents independently coordinate the whole feature?

No. The example describes two people relaying feedback between their Claude sessions. A separate agent fleet handles implementation once tickets are ready.

What outcome does the source actually document?

The author reports a working overall setup and describes Claude reviewing and revising Jira requirements. The post does not provide a shipped feature, test evidence or a measured productivity improvement.

More details

Remaining steps

  1. The colleague used their own Claude session to revise the tickets while both people relayed feedback.

About this account

Agents review ticket requirements, ask clarifying questions and begin implementation within assigned goals and context. The particular feature's completion is not established.

Firsthand account by u/Hefty_Professor_4170: https://www.reddit.com/r/ClaudeCode/comments/1xcsdco/my_claude_code_was_talking_to_his_claude_code_so/. Public RSS post and returned comments captured on 25 October 2026; RSS coverage is partial. Body eligibility passed at 0.88. Results are author-reported, not independently reproduced. Suggested prompt by Agents In Use, not the author's original prompt.

Credit: u/Hefty_Professor_4170 on Reddit

Source published

Added to Agents In Use

Source checked

Tools and topics

Claude Code · Jira · Git · Custom plugin and skills

requirements · Jira · coding-agents · human-review

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.