Skip to content

db: rename problem field to description

MusikAnimal requested to merge rename-problem-to-description into main

Fixes issue where the Description field was wiped out on every save

This fixes some fallout from !104 (merged) which was working fine, then broke massively after a botched fix of a merge conflict. This MR renames the problem field to description, and in doing so should avoid us the confusion that led to this now-fixed regression.

Note you need to run npm run reinstall-db after this change.

Bug: T369494

Edited by MusikAnimal

Merge request reports