I am submitting this from my personal account, but this issue pertains to our enterprise license. I will request our company administrators log an issue with Atlassian support and link to this post.
The Jira project connected to the issue collector has the Description set to Required and does not allow submissions with an empty Description field. However, when the submitter enters a value for either fullname or email address, the issue collector submits the form even when the Description is empty.
I've tried to intercept this in the front end by ensuring the Description field isn't empty before submitting the form, but as the fault appears to be how Jira responds to the REST call, I'm not sure of any possible ways to do this.
The following code is similar to the default code provided by the Issue Collector page. I've removed details related to my site to show the general use case.
async function updateFieldValues(id) {
// code that updates fields
// when description is empty, it is set to null
window.ATL_JQ_PAGE_PROPS.<<field name>> = <<default value>>
window.ATL_JQ_PAGE_PROPS.description = null
}
$(async () => {
$.ajax({
url: "<<issue collector hostname/collector id>>",
type: "get",
cache: false,
dataType: "script"
})
window.ATL_JQ_PAGE_PROPS = $.extend(window.ATL_JQ_PAGE_PROPS, {
triggerFunction: function (showCollectorDialog) {
$("<<element identifier>>").on('click', async function (e) {
e.preventDefault()
await updateFieldValues(e.currentTarget.id)
showCollectorDialog()
})
},
fieldValues: {}
})
})
1. Trigger the issue collector.
2. Leave the fields Description, Name, and Email Address empty.
3. Submit the form. The system shows the error Description is required.
4. Trigger the issue collector again.
5. Leave Description empty, and enter a value in either Name or Email Address.
6. Submit the form. The system submits the form completely without error.