| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T110818 Wrong warning level messages sent to vandals (tracking) | |||
| Resolved | Petrb | T110817 Huggle adding level one warnings incorrectly | |||
| Resolved | Petrb | T105622 Huggle added a lvl 3 warning two days after lvl 4 warning | |||
| Resolved | Petrb | T61982 Huggle adding wrong level warnings when warning users | |||
| Invalid | None | T64651 basetimestamp parameter is broken? the edit was stored even with months old basetimestamp | |||
| Resolved | Petrb | T75231 Huggle fails to send the correct warning to vandals | |||
| Declined | Petrb | T36619 Customed warn-summary makes problem | |||
| Open | None | T64698 Make it possible to specify what to do on edit conflict on action=edit | |||
| Resolved | Petrb | T113918 Huggle gave out four level one warnings instead of escalating warnings | |||
| Open | BUG REPORT | None | T234082 Different definitions of "recently warned" for IP editors and registered editors are required | ||
| Open | BUG REPORT | None | T266611 Incorrect Warning Level Given |
Event Timeline
Comment Actions
@Josve05a, this sounds interesting but there's no Description of the task. Can you tell me what you're proposing here? Thanks!
Comment Actions
This isn't a task, but a tracking task to 'collect' and ... 'track' tasks and specific events where Huggle left/are leaving wrong level warnings (level based on project templates, and previously received warnings) to users.