Bug 410833 - Changing ticket resolution from "RESOLVED NOT A BUG" to MOVED fails
Summary: Changing ticket resolution from "RESOLVED NOT A BUG" to MOVED fails
Status: CLOSED INTENTIONAL
Alias: None
Product: bugs.kde.org
Classification: Websites
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KDE sysadmins
URL: https://bugs.kde.org/show_bug.cgi?id=...
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-12 02:24 UTC by Philippe Cloutier
Modified: 2022-09-02 17:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Cloutier 2019-08-12 02:24:42 UTC
If I try fixing ticket #409930's status, by setting the Status fields to CLOSED MOVED, the attempt fails with the following error message when I use "Save Changes":
You tried to change the Resolution field from INVALID to MOVED, but only the assignee or reporter of the bug, or a user with the required permissions may change that field.

I suppose "Resolution" refers to the status, "INVALID" comes from the "NOT A BUG" value, and "the bug" refers to the issue. However, I am the issue's reporter.
Comment 1 Christoph Feck 2019-09-09 13:36:04 UTC
Try setting it to RESOLVED/MOVED, later to CLOSED/MOVED.
Comment 2 Philippe Cloutier 2019-09-22 22:28:11 UTC
(In reply to Christoph Feck from comment #1)
> Try setting it to RESOLVED/MOVED, later to CLOSED/MOVED.

That does workaround.
Thanks Christoph
Comment 3 Nate Graham 2022-09-02 17:24:20 UTC
Right now the "CLOSED" status is used to restrict non-privileged users who are abusing their accounts by repeatedly and annoyingly re-opening bugs that developers have marked as RESOLVED from re-opening them.

As such, if we allowed this, it would become easier for a bug reporter to accidentally move their bug into the CLOSED status and be unable to get it out of that. We don't want to make that easier.