-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network error SyntaxError:
when creating issue with assignees from issue template
#33521
Comments
Can you show the relevant URL and JSON response from the browser's "Network" tab? Is response text just this "Not found." string? |
I recreated the issue here: When I try to open a new issue with a non-admin account, it sends this request (I removed some CSRF token and cookie headers):
This is the reponse I get:
|
-> #33569 |
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Feb 12, 2025
…, fuzzy prompt, mirror proxy, adopt git) (go-gitea#33569) * Make artifact list output a stable order * Fix go-gitea#33506 * Fix go-gitea#33521 * Fix go-gitea#33288 * Fix go-gitea#33196 * Fix go-gitea#33561
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
One of our users has the following issue template:
The
assignees: ["Mets"]
gives error such asWhen a user tries to create the bug report. It seems to be related to the user not having the permissions to add such an assignee.
When I try to create the report on my Admin account it seems to work fine.
Gitea Version
1.23.1 built with GNU Make 4.4.1, go1.23.5 : bindata, timetzdata, sqlite, sqlite_unlock_notify
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
Trying to create issue as normal user
Created issue successfully as admin user
Git Version
2.47.2
Operating System
Ubuntu 24.04
How are you running Gitea?
Docker Compose with source of truth at https://github.com/blender/gitea
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: