10 Commits (439a54f4c0636afd56b7c3f9484602e296a65391)

Author	SHA1	Message	Date
ulferts	bf89e934b3	set the default value for newly build custom values ... Most of the time, the getter #custom_field_values is used with unbeknown to the caller will build custom values for not covered custom values. This method always assigned nil to the value of the newly build custom value when it should have used the default value. Once that is fixed, all models including acts_as_customizable will again have set the default values for custom fields correctly. This is true regardless of wether the custom value is added before or after the creation of the model. Only for work_packages is the additional method #set_default_values! required as the availble_custom_field might change during a request upon a switch in project and/or type.	4 years ago
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
ulferts	dccd6c0b92	wip - bcf api topic#create	5 years ago
ulferts	cd3ffe0cc5	adapt specs to altered interface	5 years ago
Oliver Günther	7fb86810db	Fix status and status attribute parsing in representer oncemore	5 years ago
Oliver Günther	42d34a56c3	Fix status parsing when nil ... Unfortunately, representable is broken when passing null values into the parsing representer. This will result in `property :foo` to be output as `{ foo: nil }` despite having a reader that writes other stuff.	5 years ago
Oliver Günther	e1e9edd668	Fix tests after status / explanation breakup	5 years ago
ulferts	2366d12809	add status to create project form	5 years ago
ulferts	4e5b9afef5	rename project attributes	5 years ago
ulferts	57f7da4f39	reuse project services in controller	5 years ago