ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Multiselect custom fields (Feature #141)
There is a long awaited feature for redmine that many people would like to see in ChiliProject, it's a 3 years old issue on the redmine official tracker.
The objective is to allow multiselect option for Custom Fields. We are using it extensively but in 3 years, the patch has never made it to upstream.
That would be awesome to have this feature upstream on ChiliProject
The Redmine issue is here : http://www.redmine.org/issues/1189
I had a look at the patch, and I'm a little underwhelmed. Currently
CustomField has_many CustomValues and
Customizable has_many CustomValues, so in essence
CutsomValues is a fat join table between customizables and custom_fields. The patch introduces a new type of
CustomValue that wraps an array and tries to be smart about saving the individual values to single custom fields. This does make searching a tad easier, but feels very brittle to me, as well as a problem that already has a solution in the form of serialization.
So I guess what I'm saying is that I'd rather have
CustomValue accept multiple values than try to emulate that behavior by storing each selected value in a separate
(and while we're at it: do we have something like a "needs a design/implementation decision" state?)
I remember that patch and it felt a tad complex. Especially since Custom Fields are already pretty complex.
I wonder if we could just serialize the custom value's value? If it stores YAML in the database, then search can still pick it up (it's just plain text). (e.g.
---\n-- "Foo"\n-- "Bar" is close to the raw values)
David Prothero wrote:
Just curious if this is implemented in redmine, if/when we can expect to see it come down to ChiliProject?
We don't follow the development of Redmine anymore, so this would probably be integrated if someone adapted the change to ChiliProject and made a pull request/patch.