Actions
Feature #8945
closedError checking of regular expressions for Custom Fields
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-07-29
Due date:
% Done:
0%
Estimated time:
Resolution:
Duplicate
Description
When setting up a Custom Field with a regular expression, there appears to be no syntax checking: it is therefore possible to enter an invalid expression, which is only detected when attempting to complete the field for the first time in a issue. It would be better to check the syntax during generation of the Custom Field.
Related issues
Actions