New 'me too' function defaults to "This bug doesn't affect me" even though I filed the bug

Absolutely, this should be the default

If you report a bug in name of someone else, it still affects 1 person, so it's still rather accurate.
Since the feature isn't really tied to specific people, it doesn't matter *who* it affects, as much as how many.

It does look bizarre as it stands.

If someone reports a bug, it is more likely that the is affected by the bug than he is not affected. So this should be changed imo.

yes, the reporter should be marked as affected by default and the option to deactivate that setting

Sorry, but this bug can't be considered Triaged unless the importance is set.

Fair enough, but it also shouldn't be Incomplete unless we're waiting for more information. I think that Medium is appropriate.

Based on the definition of Triaged (information needed for a developer to
work on the bug), flipping to incomplete for lack of importance is totally
inappropriate.

It is particularly frustrating for bug reporters since we can't change it.

I was actually just about to report a bug on this. I'm glad I came across this report.

I'd really like this addressed ASAP. It is a pretty serious wart in our implementation.

The branch is ready but it missed the deadline for 2.2.3. Will land this early next cycle.

Fixed in devel r8185.

I was going to report this bug. Nice to see it's being fixed. Does the fix also handle the case where a bug I report is merged into another bug? Right now, I go to the merged bug, and see "this bug doesn't affect me", which is just as odd as seeing it on a bug I've just filed.

For "merged" you mean when a bug is marked as a duplicate of another?

Yes. That's what I meant.

So I completely agree with you: this is necessary.

Actually, the right (given that the "me too" function will be changed to default to the more likely case) would be to merge the current "me too" status of the duplicate bug report into the merged bug report. That way if the user had unchecked the "me too", that is preserved.

Note the branch for bug #505845 allows this information to flow from dupes to master; see new properties Bug.users_affected_with_dupes, Bug.users_affected_count_with_dupes, Bug.users_unaffected.