I have a general idea. When it is iterating through all the available fields returned from Jira it is checking the field.schema.type property. It appears that the schema property doesn’t exist for one of the fields in the list. It is difficult for me to determine specifically what is causing that. I don’t have a Jira Cloud instance to test against right now. There can definitely be differences between the Cloud and Server versions.

You have three options. One, you could get me credentials for your Jira instance and I could debug it. I know that is not likely, but that would allow me to implement an actual fix. Two, if you have a programming background I could direct you where to look in the EJQT code so you could debug it. I would then add the fix back to the core code so it is there for all future releases. Third, if there are fields you need made available you can add them manually in the Available Fields tab. For each field you want to add you would add a line to columns A-E. The trick there is you will need to know the specific information for each field to be able to fill in those columns which would involve making Jira REST API calls to get the info.