Skip to content

DAAC-37: Add jira recipe (hierarchical-request approach)#10

Open
mcondo wants to merge 3 commits intomainfrom
DAAC-37-jira-hierarchical-requests
Open

DAAC-37: Add jira recipe (hierarchical-request approach)#10
mcondo wants to merge 3 commits intomainfrom
DAAC-37-jira-hierarchical-requests

Conversation

@mcondo
Copy link
Copy Markdown
Contributor

@mcondo mcondo commented Feb 13, 2025

Tl;dr

Jira Json Configuration and ASCII documentation

Details

  • See folder DAAC-37-jira-hierarchical-requests, it contains two files: the Jira Json config v2, and the ascii file with the documentation

@mcondo mcondo requested a review from DavidDwyer87 April 7, 2025 20:49
@DavidDwyer87
Copy link
Copy Markdown
Contributor

Jira API v2 → v3 Migration (CHANGE-2046)

Atlassian has permanently removed Jira Cloud REST API v2 endpoints. The /rest/api/2/search endpoint now returns HTTP 410 Gone, which breaks both the jira-classic and jira REST connector datasources.

Changes made on this branch:

  1. Deleted jira/jira-v1.json and jira/jira-v1.asciidoc (legacy serviceEndpoints-format config)
  2. Renamed jira-v2.jsonjira-v3.json and jira-v2.asciidocjira-v3.asciidoc
  3. Updated all endpoints from /rest/api/2//rest/api/3/:
    • /rest/api/2/search/rest/api/3/search/jql (path changed, not just version bump)
    • /rest/api/2/project/search/rest/api/3/project/search
    • /rest/api/2/issue/{id}/comment/rest/api/3/issue/{id}/comment
    • /rest/api/2/issue/{id}/worklog/rest/api/3/issue/{id}/worklog
    • /rest/api/2/issue/{id}/rest/api/3/issue/{id}
    • /rest/api/2/attachment/content/{id}/rest/api/3/attachment/content/{id}
  4. Updated documentation with deprecation note referencing CHANGE-2046

Related: DAAC-674
Migration guide: Jira API Migration Guide

* DAAC-674: Add Jira v3 REST configuration and documentation

* DAAC-674: Migrate Jira REST configuration from v2 to v3 and update documentation

* DAAC-674: Remove v1 and v2 Jira configurations, replaced by v3

* remove the service endpoint
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.

2 participants