Last modified: 2014-02-09 04:21:34 UTC
Title says it all
Need to consider if the OBOL should be effected by the Echo blacklists or not.
Yeah, this might be a feature instead of a bug. Needs more thought.
(In reply to comment #0) > Title says it all OBOL is Orange Bar of ... Love? Please avoid initialisms in bug summaries. The bug summary really doesn't say it all. Please try to file bugs with, at a minimum, a copy of the bug summary. Bug summaries change often, but comment 0 is forever. :-)
I'm not sure what your refering to in regards to the bug summary? From the context of your statement it appears to be neither the title or comment 0, so i'm a bit lost.
(In reply to comment #4) > I'm not sure what your refering to in regards to the bug summary? The bug summary is the field at the top of every bug next to the bug number. For this bug (bug 48691), the current bug summary is "Users Blacklisted from creating notifications still trigger OBOL when posting to a user talkpage." You can see the bug summary labeled as such by clicking the "(edit)" link next to it, which reveals the preceding text "Summary:". Comment 0 is the bug description. It's also labeled as such. This bug had two issues when filed: 1. The bug summary shouldn't use unexplained initialisms (such as "OBOL"). Currently this bug still doesn't define what an "OBOL" is, though it's also referenced in comment 1. 2. The bug description (comment 0) should, at a minimum, duplicate the bug summary. That is, please don't create a bug with a description that reads "what it says on the tin" or "as the title suggests" or "." or "title says it all". Having a useful comment 0 is much better than an useless comment 0, particularly as the bug summary can often change over time.
Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/214
