Components value auto-populating from URL request, then throws form validation error.

Eric Culley

Hey team, I'm writing a script to auto-populate a Jira service desk form from a Google document by constructing a url following this document: https://confluence.atlassian.com/servicemanagementserver/setting-up-request-types-939926357.html

Everything works as expected so far except the components values.

For example, a url like this (https://company.atlassian.net/servicedesk/customer/portal/XX/group/XX/create/XXX?summary=Test%20Summary&description=Test%20Description&priority=2&components={component_number}&customfield_10302=https%3A%2F%2Fexmaple.com) would populate the form correctly showing the appropriate value in the input that correlates to component={component_number}, but on submission it throws an error. In the UI the error reads, "Please provide a valid value for field 'Team'" (I've confirmed the values are correct) and in the network history the error shows 400 Bad Request, and the post data shows components: [object Object] instead of the appropriate value.

The weirdest part of the behavior is if I remove the components value and re-enter the same value, it allows a submission. Also, adding another components value to the input (resulting in multiple components) and then deleting it, never changing the original input populated by the URL query string params, allows form submission too! 

Am I missing something or is the components field not supported for this type of form auto population (I noticed components are not listed under field type in the doc linked above)? If it's not supported currently, are there plans to have this field type supported / can I make this a feature request?  Thanks!

Darryl Lee

Hey neat. I didn't even know about the auto-populated fields via URL feature.

So I tested with the bare minimum of Summary, Description, and Components, and I did not get an error when submitting a request! Yay!

But also, Components did not get set. Boo!

When I look at the Payload of the request, I too see the [object Object] submitted for components, whereas when manually setting the component I see the ID 10040 as expected.

So unfortunately it seems that while the UI is correctly identifying and showing the right component from the URL, that data is not getting stored properly for submission. This looks like a bug to me, and filing a Support ticket is probably the correct way to get it fixed.

I would mention in the ticket that @Christian Schaal has added a recent comment on JSDCLOUD-4049 that sounds a lot like the problem you're having. 

I did want to say though that I don't get any errors about Team. That would seem to indicate that you have a required Team field that is not getting populated? I would double-check the form and all of your customfield IDs.

Or wait, on your request form does Team = Component? If so then you're definitely running into the same problem as Christian.

If you do manage to get them to file a bug for this, be sure to come back and let us know the ID so we can upvote it. :-}