Update: Qualys Jira Connector Error: Fails to validate "Vulnerable Host" issue type

[Sonal Malik]

Hi everyone,

I wanted to provide an update on our Qualys-Jira Connector implementation.

Good news: We were able to successfully establish the integration between Qualys and Jira. Authentication, project mapping, and issue creation are now working correctly.

However, we are still facing some challenges:

• The connector is not populating all of the vulnerability information we expected to see in Jira issues.
• During configuration and synchronization, the connector continues to request the creation of additional custom fields, even after the required fields have already been mapped.
• It is not always clear which fields are mandatory from the Qualys side versus which fields are expected by Jira Service Management.
• As a result, we are seeing incomplete data being transferred from Qualys into Jira.

We have already:

• Configured the project and issue type mappings.
• Created and mapped the custom fields identified during the initial setup.
• Verified that the service account has only the necessary project-level permissions.
• Confirmed that issue creation from Qualys to Jira is functioning.

At this point, we are trying to understand:

1. Has anyone experienced the connector repeatedly requesting new custom fields even after successful integration?
2. Is there a definitive list of Qualys-required Jira custom fields for the Vulnerable Host issue type?
3. Are there known limitations regarding which vulnerability attributes are synced from Qualys to Jira?
4. Have others had to create additional Jira fields beyond those documented by Qualys to achieve a complete data sync?

Any insights, lessons learned, or best practices from your implementation would be greatly appreciated.

Thank you!

Hi everyone,

We are currently setting up the Qualys integration with Jira using the Qualys Jira Connector. We have configured the project and custom fields, but we keep running into errors during issue creation.

Based on our logs, here is what is currently working:

• ✅ Authentication is successful.

• ✅ The target project (SPACE In Jira) is successfully found.

• ✅ The connector can see our Jira project.

The Issue:
The failure occurs when the connector attempts to validate the "Vulnerable Host" issue type. It seems Qualys cannot validate this required issue type or its assignment/mapping within the JIRQ project.

Additionally, we noticed this warning in our logs:
WARN com.qualys.jiraclient.FetchJiraConfig - Note that, from v1.3.2 Jira Connector does not support Jira Admin user.
(Note: We have already ensured the service account only has project-level permissions and no global admin rights).

Our Troubleshooting Focus:
We are focusing our troubleshooting on the issue type lookup and field mappings.

Has anyone experienced this specific validation failure with the "Vulnerable Host" issue type? Are there any hidden screen, request type, or field mapping requirements in Jira Service Management that we might have missed to make this issue type visible to the Qualys connector?

Any guidance or best practices would be greatly appreciated!