Deprecated Issues V1 Endpoints
The complete list of affected endpoints and their alternatives
After careful consideration and in alignment with our efforts to enhance performance, security, and user experience, we will be deprecating certain endpoints of our Issues API in favor of more efficient and advanced endpoints available.
The affected endpoints are listed below, along with their corresponding replacements and a link to the relevant documentation.
Endpoint to be Removed | Replacement Endpoint |
---|---|
GET /api/issues | GET /api/v2/issues |
GET /api/issues/list-minimal | GET /api/v2/issues |
GET /api/revisions/:locator/revisionScan/:revisionScanId/issues | GET /api/v2/issues |
GET /api/issues/:id | GET /api/v2/issues/:id |
GET /api/count/issues | GET /api/v2/issues/types |
GET /api/v2/issues/statuses | |
GET /api/v2/issues/categories | |
GET /api/issues/status-counts | GET /api/v2/issues |
GET /api/v2/issues/statuses | |
GET /api/v2/issues/categories | |
GET api/organizations/issues/security/teams | Issue Overview UI and /issue_counts |
GET api/organizations/issues/security/release_groups | Issue Overview UI and /issue_counts |
PUT /api/issues/export-bundle | PUT /api/v2/issues |
PUT /api/issues/:id/ignore | PUT /api/v2/issues |
PUT /api/issues/:id/unlink | PUT /api/v2/issues |
POST /api/issues/csv/global | GET /v2/issues/csv/global |
We understand that these changes may require adjustments on your end. To facilitate a smooth transition, we recommend reviewing the documentation for the new endpoints provided above and updating your integration accordingly. If you encounter any issues or require assistance during this process, please do not hesitate to reach out to our support team.
We appreciate your understanding and cooperation as we work to improve our services.
Updated 5 months ago