"Easy pickings unset" is confusing lots of people
|Reported by:||lukeplant||Owned by:||nobody|
|Cc:||Triage Stage:||Ready for checkin|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
People keep getting the message "Easy pickings unset" after making a change on a ticket, and then they get confused, and sometimes they come back and 'revert' e.g.
Can someone with server access run a query to set all the NULLs for that flag to 0 or whatever the value should be?
(It is possible to do it with the batch modify interface and a query like this: https://code.djangoproject.com/query?status=!closed&easy=!1&easy=!0
But then my name will be on 1296 open tickets, which is a pain because, although I read django-updates anyway, getting e-mail personally about every ticket will break the email filters I have which currently can distinguish between django-updates and the tickets that I've actually been involved in).
Change History (5)
comment:1 Changed 4 years ago by lukeplant
- Triage Stage changed from Unreviewed to Accepted
- UI/UX unset