If the tickets are created in your Jira instance but some fields do not display data for the ticket, then do the steps that follow:
Check if your KB data is fully updated in redis DB.
You can check the checkpoint date at the following path: Docker volume path > _data > checkpoint > knowledgebase.txt.
Solution: Check for ERROR messages in the Qualys Client Service logs. If errors exist, resolve them by referring to Debugging and Troubleshooting.
Check if the fields are saved in jiraSettings.json file.
If a field is not saved in jiraSettings.json file, you will not be able to see that field in the Tickets on Jira Instance.
Jira Client may be unable to map the values because there may be spelling differences between the fields in the ticketing template and the fields in the Jira instance, such as extra white spaces, capitalization or case differences. All custom fields are case-Sensitive.
Solution: You need to modify the field name to match the exact spelling of the field name in the ticketing template.
The API response does not contain data for that field. Please check the respective detection/finding on Qualys UI to see if it contains the information missing in the Jira Instance.