Not possible to edit issue description anymore #4980

New Issue

GiteaMirror · 2025-11-02T06:09:56-06:00

GiteaMirror commented

2025-11-02 06:09:56 -06:00

Originally created by @MGChecker on GitHub (Mar 1, 2020).

Gitea version (or commit ref): 1.11.1
Operating system: Debian Buster
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL): https://try.gitea.io/cezar97/Gitea_Issue_Logout/issues/4
- No
- Not relevant
Log gist:

Description

In earlier versions, you were able to change the description of issues and PRs created by other users. This is no longer possible, which is very annoying for check lists etc.

Originally created by @MGChecker on GitHub (Mar 1, 2020). - Gitea version (or commit ref): 1.11.1 - Operating system: Debian Buster - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL): https://try.gitea.io/cezar97/Gitea_Issue_Logout/issues/4 - [ ] No - [ ] Not relevant - Log gist: ## Description In earlier versions, you were able to change the description of issues and PRs created by other users. This is no longer possible, which is very annoying for check lists etc.

GiteaMirror added the issue/regression type/bug labels 2025-11-02 06:09:56 -06:00

GiteaMirror closed this issue

2025-11-02 06:09:56 -06:00

GiteaMirror commented

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

@jolheiser commented on GitHub (Mar 1, 2020):

This is possible if you are either an admin, or in an org team with the appropriate permission for modifying issues.

EDIT: My apologies for not re-reading the whole issue. The above applies to titles, but not the description as mentioned. (At least for org teams. I assume it still works fine for admins)

@jolheiser commented on GitHub (Mar 1, 2020): This is possible if you are either an admin, or in an org team with the appropriate permission for modifying issues. EDIT: My apologies for not re-reading the whole issue. The above applies to titles, but not the description as mentioned. (At least for org teams. I assume it still works fine for admins)

GiteaMirror commented

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

@lunny commented on GitHub (Mar 2, 2020):

Posters and those who has write permissions to issue unit of the repository should be allowed to edit the issue descriptions.

@lunny commented on GitHub (Mar 2, 2020): Posters and those who has write permissions to issue unit of the repository should be allowed to edit the issue descriptions.

GiteaMirror commented

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

@MGChecker commented on GitHub (Mar 2, 2020):

@guillep2k I think this is actually a regression.

Yes, they should be, but they are not in my experience. (I just realized, my example on try. is misleading there). Even though I am able to change labels, milestones, etc. I can not edit the issue description.

@MGChecker commented on GitHub (Mar 2, 2020): @guillep2k I think this is actually a regression. Yes, they should be, but they are not in my experience. (I just realized, my example on `try.` is misleading there). Even though I am able to change labels, milestones, etc. I can not edit the issue description.

GiteaMirror commented

2025-11-02 06:09:58 -06:00

@silverwind commented on GitHub (Mar 3, 2020):

Possibly related to https://github.com/go-gitea/gitea/pull/10576. Check if you see errors in the browser console related to Transition.

@silverwind commented on GitHub (Mar 3, 2020): Possibly related to https://github.com/go-gitea/gitea/pull/10576. Check if you see errors in the browser console related to `Transition`.

GiteaMirror commented

2025-11-02 06:09:58 -06:00

@silverwind commented on GitHub (Mar 4, 2020):

@MGChecker please retry on try.gitea.io

@silverwind commented on GitHub (Mar 4, 2020): @MGChecker please retry on try.gitea.io

GiteaMirror commented

2025-11-02 06:09:58 -06:00

@MGChecker commented on GitHub (Mar 5, 2020):

Possibly related to #10576. Check if you see errors in the browser console related to Transition.

There are quite some css errors, but I did not see anything mentioning transition. (This still works for issues you created, so I think probably some logic has changed there)

@MGChecker please retry on try.gitea.io

I can not really create an example that is visible to all of you, since you would need to be collaborator in the repository to see this.

However, I have recreated and confirmed this behavior here: https://try.gitea.io/MGChecker/TestIssue/issues/1

@MGChecker commented on GitHub (Mar 5, 2020): > Possibly related to #10576. Check if you see errors in the browser console related to Transition. There are quite some css errors, but I did not see anything mentioning transition. (This still works for issues you created, so I think probably some logic has changed there) > @MGChecker please retry on try.gitea.io I can not really create an example that is visible to all of you, since you would need to be collaborator in the repository to see this. However, I have recreated and confirmed this behavior here: https://try.gitea.io/MGChecker/TestIssue/issues/1

GiteaMirror commented

2025-11-02 06:09:59 -06:00

@silverwind commented on GitHub (Mar 5, 2020):

Ok thanks, so it sounds like a individual, unrelated issue.

@silverwind commented on GitHub (Mar 5, 2020): Ok thanks, so it sounds like a individual, unrelated issue.

GiteaMirror commented

2025-11-02 06:09:59 -06:00

@MGChecker commented on GitHub (Mar 8, 2020):

Thank you very much!

@MGChecker commented on GitHub (Mar 8, 2020): Thank you very much!

GiteaMirror referenced this issue

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