So far changing the status of a bug does not affect the handler. The handler is always assumed to be the person who fixes the issue, and not the person on which the bug is pending.

The concept above can equally apply to:

• When a bug is moved to ready-for-testing custom state, it should be re-assigned to a tester (which tester, how would Mantis know!!, ...)
• When a bug is put in feedback, the bug should be assigned to the reporter.
• .. and so on.

If this is to be implemented, there should be a global solution that addresses the above points, and allow such change of ownership even for custom statuses that are added by the administrators.

I was unclear. Our project is not really asking for any automatic reassignments. They want to to be able to update the bug, change the assigned-to field and add bugnotes after it has been resolved, without having to reopen the bug.

For this project, the project manager decides whether a bug is ready to be resolved, but he does not want to have to bug assigned to him. I realize he is not using the assigned-to field as it is intended, but it's what our customer wants.

The "Change Status To" button currently does or doesn't show the "Assign To" field based on the status we are changing to. The "resolved" status doesn't show it. We should probably show it and default to current user if there was no handler for the bug, or the current assigned user if it was set.

As for editing a bug after it is resolved without re-opening.

# Bug becomes readonly if its status is >= this status.  The bug becomes read/write again if re-opened and its
# status becomes less than this threshold.
$g_bug_readonly_status_threshold = RESOLVED;

# Threshold needed to update readonly bugs.  Readonly bugs are identified via
# $g_bug_readonly_status_threshold.
$g_update_readonly_bug_threshold = MANAGER;

Set back to new. No activity for almost 2 years while assigned.

The change status now always shows the assign to field.

1. If the issue is already assigned, then it will default to the same user.
2. If not assigned and current user can be assigned issues, then will default to current user.
3. Otherwise will default to not assigned.