Defect #21530

If a new boolean custom field with a default value will be added the value won't be automatically applied to all issues

Added by Nils Grimm almost 7 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Category:Custom fields
Target version:-
Resolution: Affected version:3.2.0


If later on another custom field with an default value will be added.
All issues will have the state not assigned.
Only after changing issue the dafault value will be applied.

If you're using the REST API this will cause problems because all issues have to manually set to the default value.

Two Fixes would be nice:
  1. Is there a reason why the creation of a new boolean custom field isn't automatically set on creation?
  2. Would it be possible to do this without sending for every issue an mail.

Also available in: Atom PDF