[
https://issues.apache.org/jira/browse/CAMEL-24603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18112502#comment-18112502
]
Karol Krawczyk commented on CAMEL-24603:
----------------------------------------
Picking this up, implemented as described:
https://github.com/apache/camel/pull/26175
AGENTS.md is untouched since 1d3dbc1a7348 (2026-08-31) and carries no
transition IDs, so the
request still applies. The patch adds a short block under "JIRA Ticket
Ownership", directly below
the rule that tells agents to move a ticket to In Progress: the three IDs plus
your caveat that
/transitions must still be queried, since a transition is only offered from
certain states.
Verified against this issue while it sits In Progress: JIRA offers 5 (Resolve
Issue -> Resolved),
2 (Close Issue -> Closed) and 301 (Stop Progress -> Open). 4 is not offered
from this state, which
is precisely the point of the caveat, so that one is documented from your
description rather than
from an observed response.
One point you may want to weigh in on, it does not block the PR. With the
availability check kept
mandatory, the documented IDs do not actually save a round-trip: the
/transitions response already
returns the ID of every transition it offers, so the list works as a sanity
reference rather than
as an optimization. If you would rather have AGENTS.md describe the lookup
instead (resolve the ID
by transition name, no constants in the file), say the word and I will reshape
the patch, it is
the same size of change.
_Reported by Claude Code on behalf of Karol Krawczyk_
> Document JIRA workflow transition IDs in AGENTS.md for AI agents
> ----------------------------------------------------------------
>
> Key: CAMEL-24603
> URL: https://issues.apache.org/jira/browse/CAMEL-24603
> Project: Camel
> Issue Type: Task
> Reporter: Claus Ibsen
> Assignee: Karol Krawczyk
> Priority: Major
>
> AI agents (and OSS helper commands) repeatedly query the /transitions REST
> endpoint to discover the numeric transition IDs for common CAMEL workflow
> moves (Start Progress = 4, Resolve Issue = 5, Close Issue = 2). These IDs are
> stable across the CAMEL project workflow.
> Document the transition IDs in AGENTS.md (or the AI agent guidelines) so
> agents can transition issues without an extra lookup round-trip each time:
> * 4 -> Start Progress (=> In Progress)
> * 5 -> Resolve Issue (=> Resolved)
> * 2 -> Close Issue (=> Closed)
> Note: agents should still verify /transitions before firing a memorized ID,
> since a transition may be unavailable from the issue's current state. The
> documented list is an optimization, not a substitute for the availability
> check.
> _Created by Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
