Handle Issue wich the user lost acces corect #4388

New Issue

GiteaMirror · 2025-11-02T05:49:01-06:00

GiteaMirror commented

2025-11-02 05:49:01 -06:00

Originally created by @6543 on GitHub (Nov 25, 2019).

If you have a user wich had created an issue to a reop wich is later set to private ... the user still see the issue in his activety and issue-dashboard but if he klick at it he get will get a 404

Originally created by @6543 on GitHub (Nov 25, 2019). If you have a user wich had created an issue to a reop wich is later set to private ... the user still see the issue in his activety and issue-dashboard but if he klick at it he get will get a 404

GiteaMirror added the type/enhancement label 2025-11-02 05:49:01 -06:00

GiteaMirror closed this issue

2025-11-02 05:49:01 -06:00

GiteaMirror commented

2025-11-02 05:49:02 -06:00

@6543 commented on GitHub (Nov 25, 2019):

come up in #8741 while debuging a error

@6543 commented on GitHub (Nov 25, 2019): come up in #8741 while debuging a error

GiteaMirror commented

2025-11-02 05:49:02 -06:00

@lunny commented on GitHub (Nov 27, 2019):

I think it maybe already the correct implementation.

@lunny commented on GitHub (Nov 27, 2019): I think it maybe already the correct implementation.

GiteaMirror commented

2025-11-02 05:49:02 -06:00

@6543 commented on GitHub (Nov 27, 2019):

@lunny What do you mean

@6543 commented on GitHub (Nov 27, 2019): @lunny What do you mean

GiteaMirror commented

2025-11-02 05:49:02 -06:00

@lunny commented on GitHub (Nov 28, 2019):

I mean it seems this is the right behavior of gitea. What's wrong with it?

If you have a user wich had created an issue to a reop wich is later set to private ... the user still see the issue in his activety and issue-dashboard but if he klick at it he get will get a 404

@lunny commented on GitHub (Nov 28, 2019): I mean it seems this is the right behavior of gitea. What's wrong with it? > If you have a user wich had created an issue to a reop wich is later set to private ... the user still see the issue in his activety and issue-dashboard but if he klick at it he get will get a 404

GiteaMirror commented

2025-11-02 05:49:02 -06:00

@6543 commented on GitHub (Nov 30, 2019):

I would hide issues a user had no acces anymore ... but It looks like this need a lot of code change :( and recources

@6543 commented on GitHub (Nov 30, 2019): I would hide issues a user had no acces anymore ... but It looks like this need a lot of code change :( and recources

GiteaMirror commented

2025-11-02 05:49:03 -06:00

@stale[bot] commented on GitHub (Jan 29, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 29, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:49:03 -06:00

@6543 commented on GitHub (Jan 29, 2020):

looks like nobody care of this edge case ... so I'll close this :D

@6543 commented on GitHub (Jan 29, 2020): looks like nobody care of this edge case ... so **I**'ll close this :D

GiteaMirror referenced this issue

2025-11-02 08:11:57 -06:00

Do not track edits and deletions of pending review comments #8593

GiteaMirror referenced this issue

2025-11-02 12:25:34 -06:00

[PR #3748] [MERGED] Pull request review/approval and comment on code #17069

Sign in to join this conversation.