forgejo/models/project
Gusted b1b635c1d9
fix(sec): permission check for project issue
- Do an access check when loading issues for a project column, currently
this is not done and exposes the title, labels and existence of a
private issue that the viewer of the project board may not have access
to.
- The number of issues cannot be calculated in a efficient manner
and stored in the database because their number may vary depending on
the visibility of the repositories participating in the project. The
previous implementation used the pre-calculated numbers stored in each
project, which did not reflect that potential variation.
- The code is derived from https://github.com/go-gitea/gitea/pull/22865
2025-02-08 07:22:10 +00:00
..
column.go fix(sec): permission check for project issue 2025-02-08 07:22:10 +00:00
column_test.go test: fix test linting 2024-11-11 12:44:36 +01:00
issue.go fix(sec): permission check for project issue 2025-02-08 07:22:10 +00:00
main_test.go make writing main test easier (#27270) 2023-09-28 01:38:53 +00:00
project.go chore: Remove ChangeProjectStatus 2025-01-30 12:19:59 +01:00
project_test.go chore: Remove ChangeProjectStatus 2025-01-30 12:19:59 +01:00
template.go Rename project board -> column to make the UI less confusing (#30170) 2024-06-02 09:42:39 +02:00