Jira is deprecating the Server API endpoints and the support for Server products will end on
February 15, 2024. Hence, it is recommended that all the Jira Server administrators should migrate the existing Server API with the Jira Cloud API at the earliest opportunity.
This article explains how to find the existing Jira Server API endpoints in the existing flows and replace them with the Jira Cloud API enpoints.
Additional references:
Review the Jira Cloud API documentation
- Refer to the Jira Cloud API documentation to identify the equivalent Jira Server API endpoints and to know the authentication methods.
- Before modifying the connection, export, or import, copy the path parameter and search parameter values to a reference document to back them up when replacing the endpoints, following the instructions in the next section.
Changes to make in the Celigo platform
A. Set up a connection
Connect to the Jira Cloud platform. For detailed information, see Set up a connection to Jira Cloud platform.
B. Find Jira Server API endpoints in the existing flows
To find an export/import that uses a Jira Server connection:
- Navigate to Resources > Connections.
- Search for an existing Jira Server platform connection. From the Actions overflow ... menu, select Used by. A list of all items that use this connection appears.
- Right-click the first flow step in the list and select your browser’s option to open it in a new tab.
- List all the Jira Server API endpoints currently used in your integration.
C. Find equivalent endpoints in Jira Cloud API
For each export/import that is using the Jira Server API endpoint:
- Refer to the Supported Jira Cloud API documentation to identify equivalent endpoints for each Jira Server API endpoint.
- Use the new Jira Cloud platform connection to create new exports/imports for those equivalent endpoints.
For each export containing the Jira Server API endpoint, replace and update it with the respective Jira Cloud API endpoint.
If the existing export is configured as follows:
- Connection: Jira Server
- Resource: User
- API endpoint: Default columns
Update the export as shown in the image below:
- Connection: Jira Cloud
- Resource: User
- API endpoint: Default columns
For each import containing the Jira Server API endpoint, replace and update it with the respective Jira Cloud API endpoint.
If the existing import is configured as follows:
- Connection: Jira Server
- Resource: User
- API endpoint: Set columns
Update the export as shown in the image below:
- Connection: Jira Cloud
- Resource: User
- API endpoint: Set columns
D. Test the integration
Make sure you test the updated integration with Jira Cloud API and verify that the data is transferred accurately and that the integration functions correctly.
Comments
Please sign in to leave a comment.