If you're encountering issues or unexpected behavior with the Cobalt Jira plug-ins, this article details troubleshooting steps and solutions for common problems.
- Findings are not being pushed to Jira
- Retrieving Jira Server logs for troubleshooting
- Error: This issue could not be created. Is your integration set up correctly?
Findings are not being pushed to Jira
What is Auto-Push?
If findings are pushed to Jira then the Jira ticket ID shows up next to the finding in “<Pentest>->Findings” as well as at the individual finding level. Only findings in the “Pending Fix” state are automatically pushed to Jira.
Note: If Auto-Push is activated after findings have been added to the Pentest, Jira tickets will be retroactively created.
How can I manually push findings?
If finding is not automatically pushed to Jira because auto-push is disabled or finding state is other than “Pending Fix”, then one can manually push findings by clicking on the finding and clicking on “External Issue Tracking->Create issue in Jira”.
Findings not being pushed to Jira (Auto-Push / Manual Push)
If findings are not pushed and if there is “null” pointer or “A Jira issue is being created …” message in place of Jira ticket ID either in “<Pentest>->Findings” next to concerned finding or within the finding near “External Issue Tracking” section then the plugin has failed to create ticket in Jira even though it was pushed from Cobalt platform.
Most likely the customer has a custom configuration for the selected Jira project. Get a screenshot of the Jira project that has been used for this Pentest to confirm there are no special configurations that prohibit creating tickets in Jira.
If the issue persists please follow the guide below based on the Jira version - Server or Cloud.
Jira Cloud
- Check if there are custom Jira configurations for your selected project.
- Are findings not being pushed after at least one hour?
- To help Cobalt Customer Success assist further, please provide the Jira installation configuration as seen on the Cobalt Platform by navigating to “Settings->Jira->Configuration” to show that the Pentest is configured properly.
- To check if Findings are not being pushed to Jira, navigate to a “<Pentest>->Findings-<Finding ID>” and check what shows up near “External Issue Tracking” section
Jira Server & Data Center
- Check if the integration user has the proper permissions:
- User can create tickets in the respective Jira Project
- Provide logs to your Customer Success Manager for further troubleshooting
Retrieving Jira Server logs for troubleshooting
This article describes how to retrieve Jira server logs for the Cobalt Jira plugin.
Enabling logs
-
In the top menu bar click the gear icon and the option "System”
-
In the left menu click in "Logging and profiling“
-
Scroll to the end of the page until the section that says "Default Loggers“
-
Click the "Configure logging level for another package.“ link
Type io.cobalt.jira in the pop-up form that appears and then click the "Add" button
Cobalt Jira Server plugin logs should now appear in the Jira logs.
Retrieving the logs
If you have access to the server filesystem
For finding the location of the logs you can navigate to Administration -> System -> System Info
There will likely be several logs suffixed with .[1-9] (such as atlassian-jira.log.1) to indicate the rotation. For debugging, the one without a prefix is the most recent one, i..e atlassian-jira.log.
If you don’t have access to the filesystem
In case you are unable to access the actual files, you can use a plugin to read the file and display it in Jira such as Last Log for Jira. You can use it by going to the manage apps page and clicking on Last Log -> View Log
This will allow you to search for a prefix as well. Note that the logs must be enabled from the previous step in order to see them.
Error: This issue could not be created. Is your integration set up correctly?
The above error message is typically shown if the integration setup is not correctly mapped to the associated Jira project.
Make sure the issue type in Cobalt is correctly mapped to an available issue type in the associated Jira Project. The default issue type is “Task”, if that issue type is not available in the Jira project, the mapping needs to be adjusted.
This is done by going to the Integrations page, and selecting preferred Issue type.
Comments
0 comments
Article is closed for comments.