Linking to Jira fields in Forms not working

[Richard Morgan]

I am creating a form in our service desk and I want a drop down with a list of people in Jira. But the drop down always comes out empty. I have tried different Jira fields. Always empty. Does it not work in Preview mode to test it out?

[Kerli Suve]

It might be due to customer permissions in this specific Jira Service Management (JSM) project or global permissions of the instance not only related to a Forms settings. 

In JSM project, you can choose which users people can search for - wether you have customers divided to organizations and tou would like them to see only their org people there or it is ok to see all this projects customers.  

Also in Global permissions you can choose which groups can browse users and groups generally. 

[Pramodh M]

@Richard Morgan 

May I know which fields you have tried to map it to?

If it's single option try mapping the field value to text field

Let me know 

Thanks

[Richard Morgan]

I have a field called Supervisor. The person filling in the form should be able to pick from a dropdown of people in the company (i.e. "Customer"). So I changed LINKED JIRA FIELD to Customer but then a popup comes up:

Field type will change

Linking to the Customer Jira field will change the field type.

Current field type: Single choice

New field type: Text

I am forced to change it from a dropdown to a text field. But then when I run the form I can't select a Customer. This thing seems very broken.

[Richard Morgan]

@Pramodh M Hello? 

[Richard Morgan]

@Pramodh M Can you help?

[Kenneth McClean]

@Richard MorganI'm going to answer this for anyone who comes searching for an answer, like myself.

We had a similar issue.   Our Jira Service Desk used custom fields on a ProForma form, and the custom field values were not being populated in the form that was attached to the issue that was created.  Additionally, if I went in and edited the form, the custom fields (single-selects) had no available values from which to choose.

The solution for me was to switch the form from an issue type of "Trouble" to an issue type of "Service Request".

I'm not sure why this worked, to be honest. Both issue types used the same workflow.  If I come up with a more definitive answer, I'll update this post.