Which one of the version fields are you referring to here ? "Target" or "Fixed in"

EDIT:
Thinking about it, maybe you just need to change settings for g_update_readonly_bug_threshold and/or g_bug_readonly_status_threshold to something that matches your need ?

Also, but I'm not sure as I'm not familiar with the source countrol plugin, maybe you can change some settings there to set the version or use an account which has sufficient privileges to update read-only issues.

Hello dregad,
the problem is not in privileges: in source control system version can not be selected, so, when an issue is closed is assigned to no version.

A this point, if i try to edit a fixed issue, I can not assign this to a version, but I must reopen it, and refix with version assignment.

I would to assign issue to a version by edit its detail without change its status.

Best regards.

Meph

I would to assign issue to a version by edit its detail without change its status.

So, I believe you do have a "problem" with privileges - not related to the source control, but to your own Mantis profile. Assuming the following:

• commit a change in your svn
• source control plugin will change status of corresponding issue to Resolved
• $g_bug_readonly_status_threshold = RESOLVED (default)
• $g_update_readonly_bug_threshold = MANAGER (default)
• you have access level DEVELOPER

Based on the above, it is normal that you are not allowed to update the issue, have to reopen and resolve again.

If that is correct, then you need to either increase the readonly bug threshold (e.g. to CLOSED, or use a custom status), lower the update readonly bug threshold to DEVELOPER or change your access level to MANAGER.

Hope this helps.

As you have not responded to my last update, I assume that your problem is resolved. If not, feel free to reopen with any additional relevant information.