Repository navigation
feat(jira,bitbucket): format="json" and new read actions (2.158.0) - #224
Merged
Merged
Conversation
Programs that read c3_jira and c3_bitbucket, such as the Work Agents
Work page, had to parse text capped at 2400 tokens. With format="json"
the read actions return the normalized data as {"ok", "action", "data"}
under a 400,000-character cap; an oversized reply shrinks its largest
fields so it stays valid JSON, and "truncated" names them. Text stays
the default, so agents see no change. cli/tools/_json_reply.py holds the
envelope and the trimming.
Jira: get_issue asks for renderedFields and adds description_html,
per-comment body_html, the issue type, priority, status category,
subtasks, components, fix versions, due and attachment URLs. search
rows carry type, priority, status category and updated, and
validate="warn" passes validateQuery=warn. New dev_status reads the
development panel (pull requests, branches, commits) and answers
{"available": false, "reason"} when the server refuses it.
Bitbucket: get_repo adds description, default branch, browse and clone
links. New readme, get_file and pr_issues; list_branches asks for
details.
204 tests pass in the five touched test files. The full suite ran
before the version bump: 4807 passed, with 2 failures from the run
itself (version sync before the bump, which passes alone, and .wt/
worktree copies) and 4 collection errors from tests. module shadowing.
Not checked: a real Jira Data Center or Bitbucket server.
Claude-Session: https://claude.ai/code/session_01RMuoRDg9r5M8KwLwwxVFJ2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Programs that read c3_jira and c3_bitbucket, such as the Work Agents Work page, had to parse text capped at 2400 tokens. With
format="json"the read actions return{"ok", "action", "data"}with the normalized data under a 400,000-character cap; an oversized reply shrinks its largest fields and names them in"truncated", so it stays valid JSON. Text stays the default, so agents see no change.Jira: get_issue adds rendered HTML for the description and comments, the issue type, priority, status category, subtasks, components, fix versions, due and attachment URLs; search rows add type, priority, status category and updated;
validate="warn"passesvalidateQuery=warn; newdev_statusreads the development panel and answers{"available": false, "reason"}when the server refuses it. Bitbucket: get_repo adds description, default branch, browse and clone links; newreadme,get_fileandpr_issues; list_branches asks for details.Locally: 205 tests pass in the touched test files, ruff clean. The full suite ran before the version bump: 4807 passed, with 2 failures from the run itself (version sync before the bump,
.wt/worktree copies) and 4 collection errors fromtests.module shadowing. Not checked against a real Jira Data Center or Bitbucket server.https://claude.ai/code/session_01RMuoRDg9r5M8KwLwwxVFJ2