You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are using behaviours to automatically set fields on issue creation, but it is not possible to update the value of an insight field. We tried with the key, name and value of the insight object, but with no success.
We are using the method formField.setFormValue(value).
Thanks for your feedback,
This may not be possible yet. Is the Insight custom field of type "Label"? I believe behaviours are still incompatible with labels.
I am not sure what "Labels" type means for an insight custom field. My field is a standard insight field. We cannot update it using the label of the object nevertheless.
Apologies, I am not extremely familiar with 3rd party plugins.
From configuring the insight plugin myself in my Jira instance, I also cannot set the value on the FormField. Behaviours don't seem to be fully compatible with Insight custom fields, which is also something we see with nFeed custom fields as well.
Since behaviours don't seem like they'd work here, would a workflow post-function on the issue create step work for your use-case?
I could make up the whole thing with text custom fields and an appropriate post function, but this is far from optimal.
The context is a servicedesk project, and we really need a bunch of auto-populated fields related to the contact/user behind the request.
Do you think this is an evolution worth considering ? I believe Insight is the most popular CMDB add-on out there.
In your case, I would connect with Scriptrunner to add support for our custom field, as I think it should be possible. We're not using a label field so to say, not sure what they mean. What we store in the custom field is simply the object key for the object selected. So it should be possible for them to add support for the field.
If they need some information from us, we will provide that to help them with the implementation.
Could you post this question through our support portal? We'll investigate it further and if necessary we will open a new development issue for Insight compatibility if it does not already exist.