jira.text.field.character.limit is respected for description, environment, comments.

However some add-ons could use a large custom field instead of their own database table to track things so having jira.text.field.character.limit affect custom fields by default is risky.

Propose new jira.text.field.character.limit.customfields (so it falls right next to existing) it should default to 0 as well.

Bonus: This way a jira-system-administrator can control it above a jira-administrator who may be making custom fields and not always understanding implications.

There is already a request for setting limits on a single custom field (especially at least at creation). vs Hack of of making a field a system field...