It should be possible to clear the "r" flag somehow, after manual intervention. One alternative might be to respect the rc_patrolled flag in our filter, so "r" disappears once the edit has been reviewed. In any case, we should not require that editors perform two actions to clear both the patrolled and "r" flags.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T120923 Ask for consensus to enable and deploy ORES extension to production | |||
| Resolved | awight | T121589 mw-ext-ORES should play nice with patrol flags |
Event Timeline
Comment Actions
I talked with @Halfak about this and I thought playing around with patrol status would be best option.
Creating several patrol status would be annoying for users but when a patrol marks an edit as patrolled, we don't show the "r" sign anymore. It can be pretty helpful.
There should be a two conditions for showing the "r" sign. 1- Score passing the threshold 2- it's not patrolled. Then we can query the database and find out our false positives much easier.
It also can be something optional, let user choose when "r" will be showed, maybe someone doesn't trust the patrol system. (we can let user determine the threshold too but it's not in scope of this task obviously)
Comment Actions
Change 264293 had a related patch set uploaded (by Ladsgroup):
Don't show the r flag when edit is patrolled