Skip to content

fix(jira): use correct API URL for create_version on Server/DC#1281

Open
Mrflatt wants to merge 1 commit intosooperset:mainfrom
Mrflatt:fix/create-version-server-dc
Open

fix(jira): use correct API URL for create_version on Server/DC#1281
Mrflatt wants to merge 1 commit intosooperset:mainfrom
Mrflatt:fix/create-version-server-dc

Conversation

@Mrflatt
Copy link
Copy Markdown

@Mrflatt Mrflatt commented Apr 17, 2026

Description

The create_version method in JiraClient hardcoded /rest/api/3/version which only exists on Jira Cloud. On Jira Server/Data Center, the API uses /rest/api/2/version, causing the call to silently return None and fail with Unexpected response from Jira API: None.

Use resource_url('version') to resolve the correct API version per platform automatically (api/2 for Server/DC, api/3 for Cloud).

Fixes: #

Changes

  • Replace hardcoded /rest/api/3/version URL with self.jira.resource_url("version") in JiraClient.create_version

Testing

  • Unit tests added/updated
  • Integration tests passed
  • Manual checks performed: Verified create_version works on Jira Server/DC via MCP tool call (jira_create_version), confirmed version is created successfully with correct name and release date.

Checklist

  • Code follows project style guidelines (linting passes).
  • Tests added/updated for changes.
  • All tests pass locally.
  • Documentation updated (if needed).

The create_version method hardcoded /rest/api/3/version which only
exists on Jira Cloud. Use resource_url('version') to resolve the
correct API version per platform (api/2 for Server/DC, api/3 for
Cloud).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant