@GihanFernando My use case is to help admins manage the boards in their instance by providing them with data on board usage, including the total issue count. This is so that they can find and remove low/no-use boards to simplify their configuration
Hey @ac-tom, thanks for the extra context around your particular use case. The total count of can be obtained using the approximate-count endpoint.
Thanks @GihanFernando. Please could you advise on the form of JQL query to use? As far as I’m aware it’s not possible to search for boards directly with JQL, which means I would need to first get the filter associated with the board (using GET /rest/agile/1.0/board/{boardId}/configuration) and then use the approximate count endpoint to do a JQL search of the form filter = <filter ID>. In other words, this doubles the number of requests required to get the total issue count for a board, given its ID. Is there any alternative?
Hey @ac-tom, we’re looking into this a bit further to assess its feasibility. We haven’t got more information just yet, but will update here once we do. Just wanted to reply so that you know we’re still looking at this.
Hey @ac-tom, regarding the endpoint you’re interested in GET /rest/agile/1.0/board/{boardId}/issue (get issues for board) we noticed it excludes issues of type ‘Epic’. Using the proposed alternative approximate-count with a JQL referencing the filter (e.g. filter = <filterId>), it includes Epic issues, so the counts would differ in this context. Once this RFC is resolved (26 Feb 2026), we’ll share a suggested alternative for the count. Thanks for sharing your use case.
Thank you for your feedback. We appreciate you taking the time to share your thoughts. We heard there is a need for the reconcileIssues parameter and total response field. We discovered that using the approximate-count endpoint as a method to retrieve the total produces differences in some cases. We are exploring options to provide this response field where needed. Expect an update by late March to mid-April detailing the new endpoints replacing deprecated ones and any additional required endpoints.