Hi folks, I've read all the Vertuna documentation on how to read JSON and access the value of my Jira Custom Field but I'm still getting nothing. I need the value of customfield_31501. It's a text field. In my confiform I've tried the following:
‘ConfiForms Rules for Field Definition’ Macro
and setting Action To Execute to Set Value and Values to Set to JiraCustomField1=[entry.JiraID.fields.customfield_31501.value]
customfield_33800": null, "customfield_33801": null, "customfield_31501": "F638141, 24.3 Build & Release", "archiveddate": null, "customfield_10204": null,
Anyone out there have any ideas? Alex?
Thank you!
Hi @Nat Grauman
It is either
[entry.JiraID.fields.customfield_31501]
if you want to set it via the set value into an extra field or just using it directly through the JiraID field in the views, by having just a ConfiForms Field macro with a field name set to
JiraID.fields.customfield_31501
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried the same thing by setting the value as you suggested first, but still nothing coming through in the view. What else could I try?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is not much to "try" - this is core functionality and "just works"
Could you share how the JiraID field is configured and if you are NOT limiting the fields that should be loaded?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Alex, here is the Jira ID set up. I actually wasn't aware I needed to specify the customfield31501 here but I did, and it's still not pulling it in. FWIW here are all the values we have in there: Key,summary,status.name,priority,assignee,customfield_27841,customfield_31400, customfield_31401, customfield_31402, customfield_31403, customfield_31800,labels,customfield_31700,customfield_31702,fixVersions, customfield_20212,customfield_31501,issuelinks
Thank you for your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you try removing all what you have in there snd leaving the parameter empty?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alex - my colleague Jim helped me. He changed the order of items in the JiraID field include list and it worked. That doesn't make sense, unless we had gone past some limit. If so, we might have to take off the field include list entirely but we are struggling with slow performance overall as our confiform is getting a lot of use. It would be helpful to have a way to put it blank if the value was null , could you let us know if there is a way?
Also any other tips and tricks or docs about ways we can improve performance?
Thanks for all your help - love confiforms.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Macro parameters do have limits on length, but those are much higher
What ConfiForms does is it passes this parameter to https://docs.atlassian.com/software/jira/docs/api/REST/9.17.0/#api/2/issue-getIssue (as "fields" parameter)
But first, the same is done to load issues in bulk. And only if for some reasons that call fails it goes with a fallback algorithm and tries to load issues one by one.
However, it is hard to know in advance what needs to be optimized - feel free to open a support ticket with us to research further https://wiki.vertuna.com/display/VERTUNA/Support+Request+Form
Also, great to know the numbers to have some evidence to work with - enable logging first, https://wiki.vertuna.com/display/CONFIFORMS/How+to+enable+debug+logging+for+ConfiForms+app to see where ConfiForms struggles
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.