|· · ·|
|Open||Feature||Dreamy_Jazz||T16699 More versatile searching in CheckUser log|
|Open||Dreamy_Jazz||T204347 Duration of query recent changes in Check user tool|
|Open||Zabe||T233004 Update CheckUser for actor and comment table|
|Open||Dreamy_Jazz||T309454 cul_reason in cu_log should use the comment table|
|Stalled||None||T309982 Add cu_log.cul_reason_id, cu_log.cul_reason_plaintext_id, cu_log.cul_actor and cu_log.cul_period_id to cu_log table|
|· · ·|
I think the above ticket is a schema-change one. The patch was merged but has been reverted. I presume I will need to have the DB changes merged in then before I request it for production.
As https://wikitech.wikimedia.org/wiki/Schema_changes#Workflow_of_a_schema_change states, let's use the Schema-change-in-production once the change has been merged and not before.
I'm currently working on getting the DB changes merged into the extension. Once they are merged this task will likely include some other changes by Zabe to remove duplication of tasks. All would affect the tables created and used exclusively by the CheckUser extension. The extension has just moved to an abstract schema so this may make this process easier.