Summary
To improve performance and scalability, Atlassian is deprecating its legacy JQL search REST API endpoints. This is a mandatory, platform-wide change affecting all apps and integrations. According to Atlassian’s timeline, the shutdown process for these legacy APIs will be completed at the end of August 2025. After this transition is complete, any tool or script calling the old endpoints will permanently fail.
As a result, we are making some changes to the Timepiece REST API. Most of the Timepiece REST API integrations will be unaffected by this, but for some REST endpoints there are breaking changes. Customers using the breaking endpoints must migrate to the new endpoints as soon as possible.
Deprecated Atlassian Search Endpoints
Atlassian will remove the following legacy Jira Search API endpoints at the end of August.
Deprecated Jira Endpoints
- /rest/api/2/latest/search
- /rest/api/3/latest/search
- /rest/api/2/latest/search
- /rest/api/3/latest/search
- /rest/api/2/latest/search/id
- /rest/api/3/latest/search/id
- /rest/api/2/latest/expression/eval
- /rest/api/3/latest/expression/eval
New Jira Endpoints
Here is the new architecture called the “Enhanced JQL Service,” which uses the following primary endpoints:
- /rest/api/3/search/jql
- /rest/api/3/search/approximate-count
- /rest/api/3/expression/evaluate
Timepiece – Time in Status for Jira Cloud API Changes
We already updated Timepiece – Time in Status for Jira to use the new Jira search API for all on-screen reports.
For customers accessing Timepiece data via REST API, there are some breaking changes. Most of the new Timepiece REST API endpoints (except the ”/rest/list” endpoint) have compatible structures and they have already been modified to use the new Jira Search API.
With the new endpoints, Timepiece users will experience up to 20x performance improvements, especially for large datasets, both in the UI and via the REST API.
What do I need to do?
Customers that do not utilize the /rest/list endpoint in their integrations don’t need to take any action.
However, integrations utilizing the “/rest/list” endpoint will need to switch to the “/rest/list2” endpoint and change their paging logic.
The old “/rest/list” endpoint used to do paging with startPageIndex and pageSize parameters and supported up to 100 work items in a single request.
The new “/rest/v2/list” endpoint works with the “nextPageToken” parameter and supports up to 1000 work items in a single request. Please see the documentation for details about paging with this endpoint.
Soon-to-be-retired Timepiece Endpoint
- https://tis.obss.io/rest/list
New Timepiece Endpoint
- https://tis.obss.io/rest/list2
Migration Deadline and Required Action
Once the old Atlassian endpoints are shut down at the end of August 2025, any calls to the /rest/list endpoint will begin to fail permanently.
We urge all customers who pull data from Timepiece via the deprecated REST API endpoint to migrate their custom scripts and integrations to the new endpoint as soon as possible to ensure a seamless transition and prevent any disruption of service.
Official Atlassian Announcement
We strongly encourage your technical teams to review Atlassian’s official developer blog post for a complete explanation of this platform-wide migration.
For any questions or technical support, please do not hesitate to reach out to us via our support portal.
