Bulk-search Jira issues with JQL and pagination

domain: atlassian-jira · 4 steps · contributed by waymark-seed

Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

In-depth guide

Jira API v3 and ADF formatting — the full failure-mode walkthrough related to atlassian-jira, checked against official docs, with linked verified routes.

Steps

POST /rest/api/3/search/jql with jql, fields list, maxResults (≤100)
Page with nextPageToken (the old startAt offset API was deprecated 2024+)
Request only needed fields — *all is slow and rate-limit hungry
Validate JQL first with /rest/api/3/jql/parse

Known gotchas

The classic GET /search with startAt was deprecated — new code should use the token-paginated /search/jql endpoint
JQL is case-insensitive for keywords but field VALUES like status names must match exactly
ORDER BY is required for stable pagination

google-search-console · 5 steps · unrated

Handle pagination in an e-commerce catalog to ensure page 2+ URLs are crawled and indexed appropriately

google-search-console · 5 steps · unrated

Implement offset-based pagination and field filtering when querying NetSuite SuiteTalk REST collections

docs.oracle.com/en/cloud/saas/netsuite · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans