# Track Issues that are newly opened by the latest scan **URL:** \ **Category:** SonarQube Cloud\ **Tags:** sonarqube, dotnet, scanner, sonarqube-cloud\ **Created:** [October 14, 2026, 12:30pm UTC](https://community.sonarsource.com/t/track-issues-that-are-newly-opened-by-the-latest-scan/189841 "2026-10-14T12:30:46Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Coliwack](https://avatars.discourse-cdn.com/v4/letter/c/977dab/32.png) [@Coliwack](https://community.sonarsource.com/u/Coliwack)\ **Post date:** [October 14, 2026, 12:30pm UTC](https://community.sonarsource.com/t/track-issues-that-are-newly-opened-by-the-latest-scan/189841/1 "2026-10-14T12:30:46Z")
I’m working on an investigation where I need to investigate why the number of maintainability issues increased in my project. I would like to ask, is there a way to determine which issues were created or opened by a particular scan? We last ran the scan on 10/12, and the number of issues increased by 14. But there’s 11.9k issues in total, and it’s a lot to sort through. I want to determine if the increase was due to rule changes or if it was due to code that we produced. ---
**Author:** ![andres](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/andres/32/76342_2.png) [@andres](https://community.sonarsource.com/u/andres)\ **Post date:** [October 16, 2026, 2:26pm UTC](https://community.sonarsource.com/t/track-issues-that-are-newly-opened-by-the-latest-scan/189841/3 "2026-10-16T14:26:07Z")
Hi @Coliwack, this is possible via the [`GET api/issues/search` API endpoint](https://sonarcloud.io/web_api/api/issues/search?deprecated=false§ion=params), by filtering by creation date with one of the various `created___` parameters. However, there is one big caveat: some issues might be [backdated](https://docs.sonarsource.com/sonarqube-cloud/discovering-sonarcloud/analysis-process-overview/analysis-process#issue-backdating), and right now I’m not sure if these parameters take backdating into account or not. I will check with the team and let you know. Note: there are plans to support this in the UI in the future.