Actions
Feature #37077
open
"Unifying" core/custom field logic
Status:
New
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Description
As pointed out in #12005, the schism between "core" fields and custom fields, is quite a pain in the neck, when trying to apply plugin logic to all fields.
I have created this issue in the hopes that the Redmine dev team, would consider unifying the logic behind core and custom fields, to facilitate plugin development targeting fields, whether they be custom or "core".
Updated by David Robinson 11 months ago
Could someone reply to this?
Maybe just something simple like: Wontfix?
Actions