Helo again,
I must relativize my issue. It has no effect, if the bug has state "feedback"; so I think it has a reference to issue 0002442, which I set up many years ago.

I have the same problem in version 1.1.6 also. The "Allow Reporter to close Issue" seems has no effect. The reporter can not find any link or button to close a resolved bug which he/she reported. Do I miss any configuration? or this is a bug?

Look at this: http://www.mantisbt.org/bugs/view.php?id=10066

Same issue here (on v1.2.0rc1) : cannot set rights for reporter to close a resolved issue.

Fix suggested in note 02686 (or in 0010066) did not solve the issue for me.

same with me in 1.2.0 (release)

The linked bugfix (increase bug_readonly_status_threshold to something greater than RESOLVED) works fine for me, but I don't know if this introduces unwanted side effects.

Side effect is that all fields of resolved issues can now be updated (not just the status), which is a problem at least for me.

I have proposed a fix to allow the Reporters to close their own issues, in 0011502.

amy idea when this can be fixed? not working on 1.2.11, chema 183

Goaul,

This feature works fine for me in 1.2.11 as far as I can tell.

Please provide detailed, step-by-step instructions to reproduce the issue. Additional information listed below may also be useful:

• Relevant customizations (e.g. changes in config_inc.php, workflow, etc)
• Installed plugins or custom functions ?
• Was the MantisBT source code modified in any way ?

hello Dregad, thank you for reply.

no custom things, just using wamp to test why on production server isnt this feature working.
MySQL 5.5.24
Apache 2.2.22
PHP 5.4.3

Made flash screen recording with "Instant Demo" software so you can see what settings i have from admin acc and added config_inc.php, uploded to:
http://www.speedyshare.com/QgD85/mantis.rar

besides this from default configs in "config_defaults_inc.php" is changed this:
$g_allow_reporter_close = ON;

Goaul,

The button is not visible, because "Update Issue Status" ($g_update_bug_threshold) is set to DEVELOPER.

You probably did not realize this, because there is a known issue with the Manage Workflow Transitions page (see 0014496) which does not reflect the actual configuration (the minimum access levels at bottom of page are always shown as VIEWER).

ok thnx, now it shows, but for all reporters, not just who reported issue.
I hope there can be some workaround for that :)

Goaul, is there any chance that you can test the fixes I have implemented as described in 0014496 ? Your feedback would be greatly appreciated. Thanks in advance.

The only thing i checked was if only reporter can close his issues.
so if $g_update_bug_threshold is set to REPORTER all reporters can close, so if i need set that just reporter can close his issue what settings in config should i use as i cant get it working. in workflow that option is checked.
http://pastebin.com/BjyCf6EF

You should not set $g_update_bug_threshold = REPORTER, as it allows them to update any issue.

That said, I think there is still an issue with the code controlling when the 'Close' button is displayed, I'll look into it.

EDIT: Nevermind my above comment, I had a non-standard workflow configuration on my test project; with all config_inc.php settings as default except $g_allow_reporter_close = ON, I confirm that I get the expected behavior (i.e. 'Close' button is only visible for Reporter's own issues having a status of RESOLVED)

hmm so if i understood you correctly:
with all default params, just $g_allow_reporter_close = ON

and reporters can close their reported issues?
"(i.e. 'Close' button is only visible for Reporter's own issues having a status of RESOLVED)" - i dont get why they should able to close already resolved issue?

So what i did:

with all default settings:
$g_update_bug_threshold = UPDATER;
and
$g_allow_reporter_close = ON;

when reporter reports issue with status "new", there is no close button.
I'm doing something wrong or i misunderstood you? :/

i dont get why they should able to close already resolved issue?

resolved != closed...

when reporter reports issue with status "new", there is no close button.

correct, this is as designed.

I get the feeling that the system is not doing what you want, so why don't you start by explaining clearly and exactly what you expect.

ah sorry then i misunderstood how it should work.
So how expect it to work.
If reporter makes new issue:

1. he should able to close his issue(if needed) efen if status is new;
2. he should be able correct his issue if some information was missed, not just edit his notes(i saw this is requested feature http://www.mantisbt.org/bugs/view.php?id=8141);