0026151: Custom fields required but not displayed should be filled with the default value

ID	Project	Category	View Status	Date Submitted	Last Update
0026151	mantisbt	custom fields	public	2019-09-17 08:04	2020-06-22 06:05

Reporter	cproensa	Assigned To
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	new	Resolution	open
Product Version	2.23.0

Summary	0026151: Custom fields required but not displayed should be filled with the default value
Description	As a follow up to 0026140: In the scenario where a custom field: is configured as required is configured as not displayed has a default value the custom field still has no value for an issue. When submitting the changes for the issue, the custom field should be created with the default value.
Tags	No tags attached.

dregad 2019-09-17 08:30 developer ~0062852	I agree that this should be the system's behavior.

keessonnema 2019-10-01 07:54 reporter ~0062934	When is this feature planned to be implemented? Just for clarification.

cproensa 2019-10-04 10:39 developer ~0062945	@vboctor @atrol any objection to this? I plan to work on this as soon as i have some time (and by dependency: 0026140)

atrol 2019-10-07 16:44 developer ~0062960	No objection from my side.

zeroion 2020-02-04 15:35 reporter ~0063583	Any idea when this bug will be fixed? It's been a few months since this was reported, and this really affects usability, as we use the default text to provide guidance to our users.

keessonnema 2020-02-05 02:56 reporter ~0063585	I would like to know aswell. It would still be a great change.

keessonnema 2020-06-22 06:05 reporter ~0064115	Any updates on this?

related to	0026140	new		Custom fields are displayed on issue report even if they have disabled "Display When Reporting Issues"
has duplicate	0025372	closed	dregad	custom fields with default value unable to saved ot database if they are not on the report issue page
related to	0016011	new		Readonly custom fields and default value