Opening an issue in another repo shows all of them as "in my repos" #18913
Comments
Gusted
pushed a commit
to Gusted/gitea
that referenced
this issue
Feb 26, 2022
- Make a restriction on which issues can be shown based on if you the
user or team has write permission to the repository.
- Fixes a issue whereby you wouldn't see any associated issues with a
specific team on a organisation if you wasn't a member(fixed by zeroing
the User{ID} in the options).
- Resolves go-gitea#18913
6543
pushed a commit
that referenced
this issue
Mar 23, 2022
- Make a restriction on which issues can be shown based on if you the user or team has write permission to the repository.
- Fixes a issue whereby you wouldn't see any associated issues with a specific team on a organization if you wasn't a member(fixed by zeroing the User{ID} in the options).
- Resolves #18913
6543
pushed a commit
to 6543-forks/gitea
that referenced
this issue
Mar 23, 2022
- Make a restriction on which issues can be shown based on if you the user or team has write permission to the repository.
- Fixes a issue whereby you wouldn't see any associated issues with a specific team on a organization if you wasn't a member(fixed by zeroing the User{ID} in the options).
- Resolves go-gitea#18913
6543
added a commit
that referenced
this issue
Mar 23, 2022
- Make a restriction on which issues can be shown based on if you the user or team has write permission to the repository.
- Fixes a issue whereby you wouldn't see any associated issues with a specific team on a organization if you wasn't a member(fixed by zeroing the User{ID} in the options).
- Resolves #18913
Co-authored-by: Gusted <[email protected]>
Chianina
pushed a commit
to Chianina/gitea
that referenced
this issue
Mar 28, 2022
- Make a restriction on which issues can be shown based on if you the user or team has write permission to the repository.
- Fixes a issue whereby you wouldn't see any associated issues with a specific team on a organization if you wasn't a member(fixed by zeroing the User{ID} in the options).
- Resolves go-gitea#18913
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Gitea Version
1.16.2 + 1.17.0+dev-213-g5b0cdd615
Git Version
No response
Operating System
No response
How are you running Gitea?
codeberg deployment + try.gitea.io
Database
MySQL
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Description
if I
/issueson server)As I didn't find any notice of this behaviour in the changelog, I believe this is a bug.
Reproduce: Just create an issue in a repo that already has issues and see all of them in your Issues view. I think a similar weirdness is going on with pull requests, though I don't completely understand it yet. (I only have two repos more than I want to see, I didn't open pull requests there as far as I know, but if it was showing everything where I opened an isuse, I'm also missing some projects where I opened an issue.)
Screenshots
The text was updated successfully, but these errors were encountered: