The Kepler Custom Database plugin is terrific and lets us easily look at data from another database and put that into a child database field.
However it appears to be hardcoded to the customfieldvalue.stringvalue column in which to store its data. Since we have data longer than 255 chars, we need to store the data in the textvalue column instead.
We can't find a UI switch for this, but is there a workaround to trick the plugin into using the longer text field?
We've logged a ticket at http://bugs.kepler-rominfo.com/browse/DBCF-79but I'm posting this here in case anyone has a workaround to what has become a rather urgent last minute issue for us.
Community moderators have prevented the ability to post new answers.
As mentioned, this is tracked at http://bugs.kepler-rominfo.com/browse/DBCF-79.
I have added a comment there.
Thanks to Alexandru and his team, they created a snapshot of the next release (attached to the above Jira ticket) which does exactly what is needed: connecting the child database fields to any normal Jira field rather than the special child field type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just a remark: actually the child database fields are limited to standard jira text fields (single and multi line) and url field, beside the special database child information field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.