# Missing "author" field in api/issues/search rest API

**URL:** <https://community.sonarsource.com/t/missing-author-field-in-api-issues-search-rest-api/144030>\
**Category:** SonarQube Server / Community Build\
**Tags:** web\_api, sonarqube\
**Created:** [July 8, 2025, 12:42pm UTC](https://community.sonarsource.com/t/missing-author-field-in-api-issues-search-rest-api/144030 "2025-07-08T12:42:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![f-delahaye](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/f-delahaye/32/57915_2.png) [@f-delahaye](https://community.sonarsource.com/u/f-delahaye)\
**Post date:** [July 8, 2025, 12:42pm UTC](https://community.sonarsource.com/t/missing-author-field-in-api-issues-search-rest-api/144030/1 "2025-07-08T12:42:03Z")

</div>

Hello everyone,

We are using SonarQube Community Edition, version 25.1.0.

According to the documentation, responses for the endpoint:  
`api/issues/search?resolutions=WONTFIX&additionalFields=comments&createdInLast=1m`  
should contain the “author” field in the comments.

This was working until recently, but now the “author” field no longer appears in the response.

Switching to the new parameter `issueStatuses=ACCEPTED` (instead of the deprecated `resolutions=WONTFIX`) does not resolve the issue either.

Has anyone else experienced this, or does anyone know if this is a known issue or change in behaviour?

Many thanks in advance!

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [July 9, 2025, 2:50pm UTC](https://community.sonarsource.com/t/missing-author-field-in-api-issues-search-rest-api/144030/2 "2025-07-09T14:50:55Z")

</div>

The `author` field is only returned for **authenticated** users, so make sure you’re logged into SonarQube or authenticating your API requests with a token.

If you’re not seeing author data in your API responses, it might also be because there’s missing SCM (source control management) information for the relevant lines—SonarQube pulls this data from your version control system. If you’re scanning code that’s not in a git repository, or if you performed a shallow clone, that information may not be available.

---

<div class="post-metadata">

**Author:** ![f-delahaye](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/f-delahaye/32/57915_2.png) [@f-delahaye](https://community.sonarsource.com/u/f-delahaye)\
**Post date:** [July 10, 2025, 11:33am UTC](https://community.sonarsource.com/t/missing-author-field-in-api-issues-search-rest-api/144030/3 "2025-07-10T11:33:36Z")

</div>

Indeed, it’s working as expected with an authenticated user!

Many thanks for your help.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/system/32/31083_2.png) [@system](https://community.sonarsource.com/u/system)\
**Post date:** [July 17, 2025, 11:34am UTC](https://community.sonarsource.com/t/missing-author-field-in-api-issues-search-rest-api/144030/4 "2025-07-17T11:34:07Z")

</div>

Closed on July 17, 2025, 11:34am UTC

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.