Issue dependencies without user rights #25837
Comments
|
The languages' switching because maybe the german hasn't translate this string. |
|
@lunny I guess so too, that's why it's just a side note Is the rest a bug or intended behaviour? |
|
I have save question, I don't undestand it's feature or bug |
|
I think it's not a bug but an edge problem and no ideal resolution to fix it currently. Assume you are a plain user of this repository and issue but this issue depends on another private repository's issue but you have no permission but some others have the permissions to that dependencies issues. |
|
I have the same issue, it doesn't matter in which order the dependencies are only the first is not locked, the rest are. I can access all dependencies just fine, they are in the same repo. If I would add these dependencies in a different order and a different PR would end up in first place that would not be locked either. Also ignoring the obvious css issue.
|
|
This is most certainly a bug, considering you can just go to the issues tab of the same repository and see the issues that are locked. Furthermore if you have multiple issues blocked by a single other issue it will only show a single entry of the list of issues blocking it. |
|
I would like to have it classified as a bug, as it is really annoying and brings the feature to almost uselessness |
Fix go-gitea#27722 Fix go-gitea#27357 Fix go-gitea#25837 1. Fix the typo `BlockingByDependenciesNotPermitted`, which causes the `not permitted message` not to show. The correct one is `Blocking` or `BlockedBy` 2. Rewrite the perm check. The perm check uses a very tricky way to avoid duplicate checks for a slice of issues, which is confusing. In fact, it's also the reason causing the bug. It uses `lastRepoID` and `lastPerm` to avoid duplicate checks, but forgets to assign the `lastPerm` at the end of the code block. So I rewrote this to avoid this trick.  3. It also reuses the `blocks` slice, which is even more confusing. So I rewrote this too. 
Backport #27736 by @lng2020 Fix #27722 Fix #27357 Fix #25837 Fix #28732 1. Fix the typo `BlockingByDependenciesNotPermitted`, which causes the `not permitted message` not to show. The correct one is `Blocking` or `BlockedBy` 2. Rewrite the perm check. The perm check uses a very tricky way to avoid duplicate checks for a slice of issues, which is confusing. In fact, it's also the reason causing the bug. It uses `lastRepoID` and `lastPerm` to avoid duplicate checks, but forgets to assign the `lastPerm` at the end of the code block. So I rewrote this to avoid this trick.  3. It also reuses the `blocks` slice, which is even more confusing. So I rewrote this too.  Co-authored-by: Nanguan Lin <70063547+lng2020@users.noreply.github.com>
Fix go-gitea#27722 Fix go-gitea#27357 Fix go-gitea#25837 1. Fix the typo `BlockingByDependenciesNotPermitted`, which causes the `not permitted message` not to show. The correct one is `Blocking` or `BlockedBy` 2. Rewrite the perm check. The perm check uses a very tricky way to avoid duplicate checks for a slice of issues, which is confusing. In fact, it's also the reason causing the bug. It uses `lastRepoID` and `lastPerm` to avoid duplicate checks, but forgets to assign the `lastPerm` at the end of the code block. So I rewrote this to avoid this trick.  3. It also reuses the `blocks` slice, which is even more confusing. So I rewrote this too. 
Fix go-gitea#27722 Fix go-gitea#27357 Fix go-gitea#25837 1. Fix the typo `BlockingByDependenciesNotPermitted`, which causes the `not permitted message` not to show. The correct one is `Blocking` or `BlockedBy` 2. Rewrite the perm check. The perm check uses a very tricky way to avoid duplicate checks for a slice of issues, which is confusing. In fact, it's also the reason causing the bug. It uses `lastRepoID` and `lastPerm` to avoid duplicate checks, but forgets to assign the `lastPerm` at the end of the code block. So I rewrote this to avoid this trick.  3. It also reuses the `blocks` slice, which is even more confusing. So I rewrote this too. 
Description
When I create more than one dependence, I am not allowed to view the issue through the other issue.
Maybe this is an intended feature, but if, I don't understand this
Side note: I am using a German version, the pop up is using English
Gitea Version
1.20.0-rc1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker
Database
SQLite
The text was updated successfully, but these errors were encountered: