Get issues without epic (enhanced)
Returns all issues that do not belong to any epic. Result pagination is token based, using nextPageToken and maxResults. This only includes issues that the user has permission to view. Issues returned from this resource include Software project fields, like sprint, closedSprints, flagged, and epic. By default, the returned issues are ordered by rank. Note: If you are querying a Team Managed project, do not use this operation. Instead, search for issues that don't belong to an epic by using the Search for issues using JQL enhanced search operation in the Jira platform REST API. Build your JQL query using the parent is empty clause. For more information on the parent JQL field, see Advanced searching.
Query parameters
The token for a page to fetch that is not the first page. The first page has a nextPageToken of null. Use the nextPageToken to fetch the next page of issues.
Note: The nextPageToken field is not included in the response for the last page, indicating there is no next page.
The maximum number of items to return per page. To manage page size, the API may return fewer items per page where there is a large number of fields or properties returned. It returns max 5000 issues.
Strong consistency issue IDs to be reconciled with search results. Accepts max 50 IDs. This list of IDs should be consistent with each paginated request across different pages.
Filters results using a JQL query. If you define an order in your JQL query, it will override the default order of the returned issues.
Note that username and userkey can't be used as search terms for this parameter due to privacy reasons. Use accountId instead.
Specifies whether to validate the JQL query or not. Default: true.
The list of fields to return for each issue. By default, all navigable and Software project fields are returned.
A comma-separated list of the parameters to expand.
Response
Returns the requested issues, at the specified page of the results.