Currently, users see messages about broken constraint parameters in between regular constraint violations. This task collects improvements to this situation.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Lucas_Werkmeister_WMDE | T169532 Better treatment of constraint parameters | |||
| Resolved | Lucas_Werkmeister_WMDE | T169531 Show invalid constraint parameters on constraint statement | |||
| Resolved | Lucas_Werkmeister_WMDE | T167397 Add new constraint status for incorrect parameters | |||
| Resolved | Lucas_Werkmeister_WMDE | T169971 Make “bad parameters” results less prominent in the gadget | |||
| Open | None | T170811 Check constraint parameters after constraint statement is saved |
Event Timeline
Comment Actions
No longer in DOING/Sprint, this is mostly done and the remaining task T170811: Check constraint parameters after constraint statement is saved is lower priority IMO.
Comment Actions
I think we can close this one, the subtask is low priority and can stand on its own. The main problem of this task (“users see messages about broken constraint parameters in between regular constraint violations”) is thoroughly resolved.