[AI-61] feat: Add opt-in Jira write tools to bitwarden-atlassian-tools - #188
[AI-61] feat: Add opt-in Jira write tools to bitwarden-atlassian-tools#188SaintPatrck wants to merge 5 commits into
Conversation
`create_issue` and `link_issues` let the MCP server file and link Jira work items; `get_create_fields` reads a project's create screen first since Bitwarden's projects don't share a shape. Both write tools default to a dry run and require `ATLASSIAN_JIRA_WRITE_TOKEN` for a live write, so installs without the token stay exactly as read-only as before.
Add the jira-software issue-scope twins Atlassian actually requires, drop the classic write:jira-work callout and per-endpoint scope table in favor of a flat scope table matching the read-scope sections above, remove the classic-token mention, and add a create_issue usage example.
Correct the README/CHANGELOG/auth.ts claim that write tools are hidden without a token — they're always listed with a working dry-run; without ATLASSIAN_JIRA_WRITE_TOKEN only the live write refuses. Stop presenting a hardcoded string as a literal Jira quote in get_create_fields' 404 handling. Extract the duplicated write-token guard text into a shared write-guard util. Have link_issues read the outward issue back after a live link and report whether the direction verified. Document that a leaked write token carries unused comment/attachment scopes Atlassian requires alongside the issue scopes.
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE Re-reviewed the commits added since the previous round ( Code Review DetailsNo findings. The three suggestions from the prior round were addressed in |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
Stop rewriting a field's own name when it contains the word "type" in get_create_fields' output. Hint at partial write-token scopes instead of an unrelated field-lookup tip when create_issue/link_issues fail with Jira's generic 401. Drop the last "read-only" claims from the MCP server's own module comment and package metadata.
1 participant
🎟️ Tracking
AI-61
📔 Objective
Adds three MCP tools to
bitwarden-atlassian-tools's bundled server:create_issueandlink_issues(write, opt-in) andget_create_fields(read-only, discovers a project's create-screen requirements before drafting). Both write tools default to a dry run and require an optionalATLASSIAN_JIRA_WRITE_TOKENfor a live write; installs without that token keep today's behavior for anything that writes.