Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not possible to edit issue description anymore #10558

Closed
1 of 3 tasks
MGChecker opened this issue Mar 1, 2020 · 8 comments · Fixed by #10623
Closed
1 of 3 tasks

Not possible to edit issue description anymore #10558

MGChecker opened this issue Mar 1, 2020 · 8 comments · Fixed by #10623
Labels
issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself type/bug
Milestone

Comments

@MGChecker
Copy link

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.

@jolheiser
Copy link
Member

jolheiser commented 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)

@lunny
Copy link
Member

lunny commented Mar 2, 2020

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

@MGChecker
Copy link
Author

@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.

@guillep2k guillep2k added the issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself label Mar 3, 2020
@silverwind
Copy link
Member

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

@silverwind
Copy link
Member

@MGChecker please retry on try.gitea.io

@MGChecker
Copy link
Author

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

@silverwind
Copy link
Member

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

@MGChecker
Copy link
Author

Thank you very much!

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants