Renaming fields in dictionary does not lead to changes in related tables

[pkou <pkou at ua.fm>]

Trac does not update all affected fields when dictionary is edited.

Required additional processing for default values:

• When default component, priority, severity, version, or milestone is renamed via trac-admin, then appropriate property default_component, default_priority, default_severity, default_version, or default_milestone should be renamed in trac.ini;
• When default component, priority, severity, version, or milestone is deleted via trac-admin, then appropriate property default_component, default_priority, default_severity, default_version, or default_milestone should be cleared in trac.ini.

Required additional processing when dictionary records are renamed:

• If priority, severity, milestone, or version is renamed, then field priority, severity, milestone, or version should be renamed in appropriate tickets.

Required additional processing when dictionary records are deleted:

• If component, milestone, or version is deleted, then field component, milestone, or version should be cleared in appropriate tickets;
• If priority or severity is deleted, then field priority or severity should be renamed to default value in appropriate tickets.

Patch attached.

[pkou <pkou at ua.fm>]

Patch for the changes

[rush@…]

#447 (implemented in [691]) addresses the milestone portion of this ticket, but not component, priority, severity, version.

[Matthew Good]

The other parts of this were already addressed in [1831]