fix(blocks): correct required field validation for Jira and Confluence blocks#4172
fix(blocks): correct required field validation for Jira and Confluence blocks#4172waleedlatif1 merged 3 commits intostagingfrom
Conversation
…e blocks Jira: summary is only required for create (not update), projectId is not required for update (API uses issueKey). Confluence: title and content are required for page creation, title is required for blog post creation — all enforced by backend validation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR SummaryLow Risk Overview Updates the Jira docs to clarify that Reviewed by Cursor Bugbot for commit 57e3449. Configure here. |
Greptile SummaryThis PR fixes required-field validation mismatches in the Jira and Confluence block configs. In Jira, Confidence Score: 5/5Safe to merge — all required-field changes match documented Atlassian API contracts. All three files contain targeted, correct changes with no logic bugs, no new dependencies, and no broken contracts. The No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
subgraph Jira["Jira Block"]
JOp{operation?}
JOp -->|write / create| JReqAll["projectId required\nsummary required"]
JOp -->|update| JReqPartial["projectId not required\nsummary not required\nissueKey required"]
JOp -->|read-bulk| JReqBulk["projectId required"]
end
subgraph ConfLegacy["Confluence Legacy Block"]
COp{operation?}
COp -->|create| CReqCreate["title required\ncontent required"]
COp -->|update| CReqUpdate["title not required\ncontent not required"]
end
subgraph ConfV2["Confluence V2 Block"]
CV2Op{operation?}
CV2Op -->|create| CV2ReqCreate["title required\ncontent required"]
CV2Op -->|create_blogpost| CV2ReqBlog["title required\ncontent required"]
CV2Op -->|update / update_blogpost| CV2ReqUpdate["title not required\ncontent not required"]
end
Reviews (2): Last reviewed commit: "lint" | Re-trigger Greptile |
…re content for blog post creation Jira: Remove dependsOn projectId from shared write/update fields — projectId is not required for update so the gate would disable all update fields when no project is selected. Write-only fields (issueType, parentIssue, reporter) retain the gate since projectId is required for create. Confluence V2: Add create_blogpost to content required condition — backend Zod schema enforces content for blog post creation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
@greptile |
|
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 57e3449. Configure here.
Summary
summaryis now only required for create issue (not update — partial updates are supported).projectIdis no longer required for update (API usesissueKeyin the URL path, and the update tool doesn't even acceptprojectId).titleandcontentare now required for page creation (backend rejects without them).titleis also required for blog post creation in V2.Test plan