I am trying to make use of the new Jira portal form auto-population mechanics. (See link for more info.)
The following format works in these cases:
But when I try to do the same for a radio-button, nothing happens.
Is the guidance correct? Are additional parameters required, such as "xxxoptionid=selected"?
Are there Jira ServiceDesk settings or configurations that will prevent pre-populating a radio button?
EXAMPLE: I would expect the following to auto-populate the selection of the radio button based upon the example below:
https://<domain>/servicedesk/customer/portal/XX/create/XX?customfield_246000=23300
<fieldset class="field-group group" role="radiogroup"
aria-labelledby="customfield_24600-label">
<legend id="customfield_24600-label">RadioField</legend>
<div class="radio" resolved=""><input class="radio" type="radio"
name="customfield_24600" id="customfield_246000" value="23300"
resolved=""><span class="aui-form-glyph"></span><label
for="customfield_246000">Option#1</label></div>
<div class="radio" resolved=""><input class="radio" type="radio"
name="customfield_24600" id="customfield_246001" value="23301"
resolved=""><span class="aui-form-glyph"></span><label
for="customfield_246001">Option#2</label></div>
<div class="radio" resolved=""><input class="radio" type="radio"
name="customfield_24600" id="customfield_246002" value="23400"
checked="" resolved=""><span
class="aui-form-glyph"></span><label
for="customfield_246002">Not Specified</label></div>
</fieldset>
Any thoughts or insights?
RESOLVED:
https://<domain>/servicedesk/customer/portal/XX/create/XX?customfield_246000=23300
RADIO BUTTON ID = customfield_24600
FIRST OPTION = customfield_246000 (customfield_24600+0)
SECOND OPTION = customfield_246001 (customfield_24600+1)
***
Really easy to miss that nuance between "customfield_24600" and "customfield_246000".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.