GH-93: feat(jira): implement SyncCapable + new CreateIssue/UpdateFields + sdk/util/retry adoption#98
Merged
Merged
Conversation
…adoption (GH-93) Adds core.SyncCapable to the Jira connector: JQL-paged ListUpdatedSince/ ListAll (startAt/maxResults), GetIssue, TransitionState, AddComment with the pilot-op idempotency marker (raw-JSON substring match, ADF-safe), and new CreateIssue/UpdateFields REST calls. StateGroup maps Jira's status category onto the To Do/In Progress/Done taxonomy. doRequest now runs through sdk/util/retry with typed RateLimitError (429, Retry-After honored) and AuthError (401/403, no retry) classification, matching the GitHub connector's retry adoption.
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
1 participant
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.
Summary
Automated PR created by Pilot for task GH-93.
Closes #93
Changes
GitHub Issue GH-93: feat(jira): implement SyncCapable + new CreateIssue/UpdateFields + sdk/util/retry adoption
Context
SaaS pre-work S0.10. Implements the #83
SyncCapablecontract for Jira — the connector with real write gaps: JQL search +GetTransitions/TransitionIssueToexist, but there is NOCreateIssueand NO general field-update method (verified 2026-07-13). Also adopts the shared retry package.Depends on: #84
Implementation
In
sdk/integrations/jira:CreateIssue(POST /rest/api/3/issue) andUpdateFields(PUT /rest/api/3/issue/{key}) — plain REST, ADF or plain-text body per existing client conventions.core.SyncCapable:ListUpdatedSincevia JQLproject = X AND updated >= "<ts>" ORDER BY updated ASCpaged by startAt/maxResults;ListAllsame without the filter;GetIssue;TransitionState= existing GetTransitions→TransitionIssueTo (name-based);AddCommentwith the<!-- pilot-op:{idemKey} -->marker (Jira preserves it in ADF); mapping: StateGroup = status category (To Do / In Progress / Done), SequenceID = PROJ-42 key.sdk/util/retry(refactor(util): generalize github retry into sdk/util/retry with typed RateLimitError/AuthError #84) for all Jira HTTP calls with per-response error classification (429/Retry-After → RateLimitError; 401/403 → AuthError).Acceptance
Refs
.agent/system/saas-asset-research.md§ studio-sdk · Design: saas-kanban-sync-design.md §2/§5