We're migrating from Jira 4.4 up to Jira 6 and need to pull the values for a custom field that was a "Velocity processed Message Custom Field (for view)" field, which we'll just stuff into a plain old text field in our new Jira 6 instance. The problem is that I can't find the field values in customfieldvalue.
Where is the plugin hiding values for these custom fields?
Thanks,
Mike
I'm embarassed to say I figured this out and it was a stupid question. After looking at the default text using Nic's comment below to point me in the right direction I saw this:
#macro (getReleaseNoteComment $issue $customFieldManager) #set ($customFields = $customFieldManager.getCustomFieldObjects($issue.project.getLong("id"), $issue.issueType.getString("id"))) #foreach($customField in $customFields) #if($customField.name.equals("Fix Version Build/s")) #if($customField.getValue($issue)) <a href="https://athena.redprairie.com/hotfixes/hf_results.php?hf_num=$customField.getValue($issue)" target="_blank"> $customField.getValue($issue)</a> #end #end #end #end #getReleaseNoteComment($issue $customFieldManager)
So we were simply referencing another field's value and then processing that.
Thanks for the help!
Er, no, this is completely wrong.
There are no "values" for velocity processed fields. They don't hold any data, so customfieldvalue is empty for them.
The way they work is to process velocity that is added to their default text, which is held in the field context. I can't remember the name of the table for that off the top of my head though, sorry. But, I *think* (please, don't hold me to this!) it is genericconfiguration
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep. Saw that, but it doesn't seem to be accurate - at least for our instance. An entry does exist in customfield, but there's nothing in customfieldoption or customfieldvalue despite having thousands of issues that do have that field populated.
So it would appear that the plugin is persisting the field values somewhere else.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you will find the query in this post:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep. Saw that, but it doesn't seem to be accurate - at least for our instance. An entry does exist in customfield, but there's nothing in customfieldoption or customfieldvalue despite having thousands of issues that do have that field populated.
So it would appear that the plugin is persisting the field values somewhere else.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Those values are null in customvalue (customfieldoption), stringvalue, textvalue (customfieldvalue)?
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.
I already told you that you're looking in the wrong place.
(Edit) Sorry, that probably seems quite grumpy, I don't mean it that way. I'm afraid Mehmet is wrong about this particular type of field, and you need to read my original answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.