Fix: Migrate from Jira API v2 to v3 #513
Closed
Conversation
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
- Added cweagans/composer-patches to dependencies - Created patch to update lesstif/php-jira-rest-client to use API v3 - Changes /rest/api/2 to /rest/api/3 in JiraClient This resolves the 410 error caused by Atlassian's removal of API v2. The patch automatically updates the underlying Jira client library without requiring a fork of that dependency. Fixes compatibility with Atlassian Cloud Jira API v3.
Member
|
As mentioned in #512, this changes nothing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This resolves the 410 error caused by Atlassian's removal of API v2. The patch automatically updates the underlying Jira client library without requiring a fork of that dependency.
Fixes compatibility with Atlassian Cloud Jira API v3.