-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
- Compass Custom Incoming Webhook feature fails to parse JSON keys containing dots (periods) when using JQ-style dot notation, preventing integration with SonarQube webhooks that use keys with the prefix "sonar.analysis.*".
- Reference: https://community.atlassian.com/forums/Compass-articles/Looking-for-beta-testers-Custom-Incoming-Webhook-and-Deployment/ba-p/2870446
Additional Context:
- This issue is specific to the Custom Incoming Webhook beta feature
SonarQube webhook payload structure can't be modified to remove dots from key names due to platform constraints - This limitation likely affects other third-party tools with similar naming conventions when using the Custom Incoming Webhook feature
- Core webhook functionality works correctly aside from this JSON path parsing issue
Feature otherwise performs well for deployment event integration
Steps to Reproduce
- Access Compass Custom Incoming Webhook feature
- Configure SonarQube as a custom tool to send webhooks to Compass as deployment events
- In webhook configuration, attempt to map componentId using dot notation: .properties.sonar.analysis.componentId
- Try bracket notation: .properties["sonar.analysis.componentId"]
- Attempt other JQ syntax variations for field mapping
- Observe configuration rejection in Compass webhook configuration modal
Sample Webhook Payload { "properties": { "sonar.analysis.detectedscm": "git", "sonar.analysis.detectedci": "Github Actions", "sonar.analysis.componentId": "ari:cloud:compass:abcd-efghijklmnop:component/abcd-efghijklmnop/abcd-efghijklmnop" } }
Impact
Severity: Medium
Scope: Affects SonarQube integrations and potentially other tools using dotted key names in the Custom Incoming Webhook beta feature
Workaround: None available - SonarQube only allows custom properties with "sonar.analysis.*" prefix
Expected Results
Custom Incoming Webhook configuration should support:
Escaped dot notation for JSON keys containing periods
JQ-style bracket notation (e.g., .properties["sonar.analysis.componentId"])
Standard JSON path expressions for keys with special characters
Actual Results
Custom Incoming Webhook configuration modal rejects all syntax variations for JSON keys containing dots
Modal appears to block special characters entirely in the componentId field mapping
Cannot extract componentId from SonarQube webhook payload
Workaround
None
I've tried the alternative integrations however they don't meet the requirements of what I'm trying to do:
It's disappointing this bug won't be prioritized higher as it's arguably a necessity in a feature that aims to add extensibility to the Compass platform.