Damien Regad

Closed in favor of #1841

@vboctor @atrol can you please confirm you're OK with the latest fixes following your respetive reviews ?

Came back to this following @atrol's note in #1631. Not sure what is the status on this, @vboctor @cproensa ? Can it be merged or are you still discussing ?

@cproensa weeks have turned into months, any chance to see this finalized ?

> Fixes #25514 @obmsch I think you referenced the wrong issue Id in the PR's opening note, as well as in the original commit message... [#25614](https://www.mantisbt.org/bugs/view.php?id=25614) is about _Missing file...

> @dregad no, #25514 is correct. Nevermind me, just now I realize that I had a typo in the bug ID, and I was actually looking at #25614 :astonished:

Even if they can edit their own issues, a reporter should not be able to update an issue's status if `$g_update_bug_status_threshold = DEVELOPER;` In my test setup, it is currently...

> maybe because of setting `$g_allow_reporter_reopen = ON;`? It *is* ON (default value), and that could explain allowing a status change from (>= $g_bug_resolved_status_threshold) to NEW, but not let me,...

It's not a huge deal and I could live with it if you insist on having these function in the bug/project API, but I still feel it's confusing not to...

I have not actually tested this, but I'm fine with the approach. Considering the fact that this is a recurring problem, I believe it would be worth clearly documenting it...