Updating issue description for an issue with an associated Spam log fails
Summary
Whilst editing issue descriptions I often receive an error "Something went wrong" and the issue description is reverted. This is preventing users from updating some of their own issues and is quite a confusing failure. The error is probably ambiguous due to the fact that the issue has been detected as a spammy issue.
This has been noticed by others when checking off tasks and updating the description that way.
Marking as ham resolves the issue.
Steps to reproduce
- Pick an issue that has an associated Spam log entry in the Admin Dashboard and has associated tasks
- Feature proposals are good examples
- Update it's description
What is the current bug behavior?
Posting a seemingly innocent update to an existing issue like marking off a task fails if the issue has a spam log entry
What is the expected correct behavior?
Check off the related task list item
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
N/A reproduced on GitLab.com v9.5.1
Results of GitLab application Check
N/A reproduced on GitLab.com v9.5.1