PR https://github.com/mantisbt/mantisbt/pull/1279

Is this simply a revert?

Is this simply a revert?

No, a revert would reintroduce 0023420.

The difference is the first parameter of bug_monitor calls.

@atrol, I just noticed with a bit of surprise as I resolved 0032840 as duplicate of a Closed issue 0028803, that I got automatically added to the monitoring list, due to the changes introduced by MantisBT master-2.10 3e51ee66.

I don't really see the point of monitoring a closed issue, as it is unlikely that it would become active again. It may (possibly) make sense for the reporter, "just in case" (e.g. the issue is reopened, or like me here, a note is added some years after), but from a developer's standpoint (handler) I see no benefit to justify it.

What do you think ?

Agreed @dregad also as our default "Monitored by Me" filter hides status "Closed".

@dregad I don't think it hurts. Take this scenario:

• You reported an issue X.
• It got marked as a duplicate of closed issue Y and you (the reporter) were added to issue Y which was recently closed as fixed.
• Issue Y was re-opened due to a discover issue.
• The reporter of X gets notified and it shows on their monitored list.

Now if nothing happens, then it won't show on your monitor list or cause any extra notifications.

Anyways, I think it is the current behavior and not really much downside. So it is "just in case" as you said.

Yes for the reporter
I was talking about the handler (i.e. the dev who resolves the duplicate issue)

Actually thinking about this some more, what I believe does not make sense, is to add the issue's handler, when they are also the user resolving the issue.