The UserVoice ID custom field isn't really intended to be a field the user interacts with directly. It's used under the hood. When you initially configure the plugin, we do a lot of behind the scenes setup to make certain the field has all the things it needs to function in JIRA, so we recommend leaving the field's configuration as is. So, in short, the things we need from the field are happening, so we haven't spent a lot of effort focusing on the user interaction aspect of the field, since it wasn't a primary goal. If there's a particular feature that having access to the field data would be useful for, please let us know and we'll consider it for the future.
A comment to an existing feedback should be added as a comment to the existing JIRA issue. Sounds like there might be a config issue going on with your setup. Let's take this offlist. Can you email email@example.com a screenshot of your plugin config page, and the following info: which version of the plugin you're using, which version of JIRA you're using, and attach a support zip (so we can review your JIRA logs) which you can get from your JIRA admin console. Cheers, Laura
In a first moment I think that this can be related with some behaviour of the plugin (but can be a expected or unexpected behaviour), so as this is a third-party plugin, I would suggest you to make a contact with the App Fusions to obtain a better clarification about this topic, you can contact them by the following:
I hope this helps.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs