bug: double plus encoding in search query

[praaatap]

Bug Description

There are two critical logic errors in how the GitHub Search API queries are constructed in scrumHelper.js:

1. Double Plus Encoding: When an organization is specified, the query adds an extra + sign resulting in ++org%3A{orgName}. This is malformed syntax for the GitHub API.

Steps to Reproduce

Steps to reproduce the behavior:

1. Open settings.
2. OR enable "Use Repository Filter" and select a repository name.
3. Click "Generate Report".
4. Check in Network tab of chrome dev tools to see the malformed query.

Expected Behavior

1. The organization query should be correctly formatted with a single +.

Additional Context

The fix involves ensuring orgPart does not have a leading + before being concatenated.

---

Contribution Checklist

• I have searched existing issues to ensure this bug hasn't been reported
• I have provided clear reproduction steps
• I have included relevant environment details
• I have described both expected and actual behavior

[vedansh-5]

Thanks @praaatap for your contribution. Please add a video reproducing the bug. I can not reproduce the bug with the above mentioned steps.

This is on master branch. I don't see the bug above.

[kaungmyatshwe1397]

@vedansh-5 I am still able to reproduce the 422 error on latest master and working on this too,
Steps: leave org empty, select date range, enable filter or not ,click Generate Report.
The API returns JSON messages, but the report generation fails and the console shows a 422 error (see attached screenshots).
Please let me know if I might be missing something.

[vedansh-5]

Thankyou @kaungmyatshwe1397 for your response.

Am I missing something?

[kaungmyatshwe1397]

@vedansh-5 I believe the 422 error is caused by a change in GitHub’s Search API behavior when a user access token is present.

• When no token is used, the current search query works and returns results normally.
• When a token is included, GitHub requires the query to explicitly include either:
  • is:issue
  • is:pr or is:pull-request

With authentication, the API only allows searching issues or pull requests separately, not both in a single query. To retrieve both, we must send separate queries.

This behavior aligns with the current GitHub REST API documentation for authenticated search requests.

I confirmed this using Postman:

• The same 422 URL works when no token is sent.
• Postman requests succeed because no authentication token is attached.
• When the token is removed from scrum_helper, the report works without a 422 error.

query status :200 in postman .

same query but fail with 422 due to having token

query status with (is:issue) :200 in postman means access token is the main possible cause for this current 422 error.

Therefore, the root cause appears to be GitHub’s authenticated search restrictions for requests made with a user access token.

Proposed Fix

When a token is detected:

• Split the search into two separate queries:
  • One with is:issue
  • One with is:pull-request
• Merge the results before generating the final report.

Alternatively, introduce a conditional flow:

• If a token is present → enforce the is: qualifier in the query.
• If no token is present → maintain the current behavior.

I can proceed with implementing this fix upon approval.

[vedansh-5]

Thanks @kaungmyatshwe1397 now its clear to me. The error is not due to any change in GitHub’s Search API behavior. It occurs because a fine-grained PAT is being used. The extension is currently configured to work with a classic personal access token, not a fine-grained one.
I have verified this behavior using postman.

Using classic token

Using fine-grained token (same query)

The README previously mentioned using a classic token, but it seems that instruction was overwritten. I’ll update the README again to avoid further confusion.
I’ll also update this issue’s description accordingly, since Bug 1 is still valid and needs to be addressed. @praaatap Please raise a PR for Bug 1.