View Issue Details

IDProjectCategoryView StatusLast Update
0026151mantisbtcustom fieldspublic2019-10-07 16:48
Reportercproensa Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version2.23.0 
Summary0026151: Custom fields required but not displayed should be filled with the default value

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.

TagsNo tags attached.


related to 0026140 new Custom fields are displayed on issue report even if they have disabled "Display When Reporting Issues" 
has duplicate 0025372 closeddregad 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 




2019-09-17 08:30

developer   ~0062852

I agree that this should be the system's behavior.



2019-10-01 07:54

reporter   ~0062934

When is this feature planned to be implemented? Just for clarification.



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)



2019-10-07 16:44

developer   ~0062960

No objection from my side.

Issue History

Date Modified Username Field Change
2019-09-17 08:04 cproensa New Issue
2019-09-17 08:04 cproensa Relationship added related to 0026140
2019-09-17 08:06 dregad Relationship added has duplicate 0025372
2019-09-17 08:07 dregad Relationship added related to 0016011
2019-09-17 08:30 dregad Note Added: 0062852
2019-10-01 07:54 keessonnema Note Added: 0062934
2019-10-04 10:39 cproensa Note Added: 0062945
2019-10-07 16:44 atrol Note Added: 0062960