Closed disco-lance closed 2 years ago
Whats weird is that if it was most of the common things, it would report more field errors. The field in question appears to be the vulnerability summary field. The logs indicate that it exists and is in the appropriate screens.
2021-09-30 16:23:28,084 tenable_jira.jira.Jira INFO Vulnerability Severity is customfield_12422 (existing)
Can you manually check in Jira to see if anything looks odd?
Sorry for the delay on getting back on this. So far everything looks good in Jira. We checked Vulnerability Severity and it does show on both the creation and updating screens.
Yeah this is really weird. if Jira complains about the screens, it'll typically complain about a lot more than just one field. The logs say that the field is properly linked into the screens on the right tab. The ticket creation from the logs looks correct. Could it be a permission issue?
No permissions issues that I can see. The account is a site admin, project lead over VULN, and an administrator of the project. I'm really at a loss for this, it seems like everything is there that it needs.
Is this a new setup, or an existing one?
New setup. If we need to restart the process, we can. Not sure what we need to clear out to start fresh.
I would first start out with creating a separate project and see if that properly links in. Just add a key and name to the project definition and the next run will create a whole new project instead:
project:
key: VMNGT
name: Tenable Vulnerability Management Project
If that works, then you can safely delete the old project. The nuclear option is to delete the project, fields, and screens.
Looks like a different error, but still an issue with customfield_12422.
2021-10-13 13:38:38,556 restfly.errors.BadRequestError ERROR [400: POST] https://
jira:
address: <REDACTED>
api_token: <REDACTED>
api_username: <REDACTED>
project:
key: VMNGT
leadAccountId: <REDACTED>
name: Tenable Vulnerability Management Project
screen:
jira_ids:
- 11767
- 11768
tenable:
access_key: <REDACTED>
address: <REDACTED>
platform: tenable.sc
query_id: 2147
secret_key: <REDACTED>
2021-10-13 13:38:30,842 root INFO Tenable2JiraCloud Version 1.2.2
2021-10-13 13:38:30,842 root INFO Using configuration file config.yaml
2021-10-13 13:38:30,842 root INFO Running on Python3.9.7Windows/AMD64
2021-10-13 13:38:30,842 root DEBUG Severity Prioritization set to: {'critical': 1, 'high': 2, 'medium': 3, 'low': 4}
2021-10-13 13:38:30,842 tenable.sc.TenableSC DEBUG {"method": "GET", "url": "https://<TENABLE_SC_HOST>:443/rest/system", "params": {}, "body": {}}
2021-10-13 13:38:30,858 urllib3.connectionpool DEBUG Starting new HTTPS connection (1): <TENABLE_SC_HOST>:443
2021-10-13 13:38:30,920 urllib3.connectionpool DEBUG https://<TENABLE_SC_HOST>:443 "GET /rest/system HTTP/1.1" 200 None
2021-10-13 13:38:30,920 tenable_jira.jira.Jira DEBUG Request: {"method": "GET", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/project/VMNGT", "params": {}, "body": {}}
2021-10-13 13:38:30,920 urllib3.connectionpool DEBUG Starting new HTTPS connection (1): <JIRA_CLOUD_HOST>:443
2021-10-13 13:38:31,155 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "GET /rest/api/3/project/VMNGT HTTP/1.1" 200 None
2021-10-13 13:38:31,155 tenable_jira.jira.Jira DEBUG Request: {"method": "GET", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/field", "params": {}, "body": {}}
2021-10-13 13:38:31,421 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "GET /rest/api/3/field HTTP/1.1" 200 None
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Tenable Platform is customfield_12388 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO CVEs is customfield_12389 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO CVSSv2 Base Score is customfield_12390 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO CVSSv2 Temporal Score is customfield_12391 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO CVSSv3 Base Score is customfield_12392 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO CVSSv3 Temporal Score is customfield_12393 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Patch Publication Date is customfield_12394 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Tenable Plugin ID is customfield_12395 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Tenable Plugin Family is customfield_12396 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Tenable Plugin Name is customfield_12397 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Vulnerability Severity is customfield_12422 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Finding Severity is customfield_12447 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Tenable Asset UUID is customfield_12399 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Tenable Asset Tags is customfield_12400 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Device MAC Addresses is customfield_12401 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Device IPv4 Addresses is customfield_12402 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Device IPv6 Addresses is customfield_12403 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Device Hostname is customfield_12404 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Device NetBIOS Name is customfield_12405 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Device DNS Name is customfield_12406 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Device Network ID is customfield_12407 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Vulnerability First Seen is customfield_12408 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Vulnerability Last Seen is customfield_12409 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Vulnerability Last Fixed is customfield_12410 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Vulnerability State is customfield_12411 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Vulnerability Port is customfield_12412 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Vulnerability Protocol is customfield_12413 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Vulnerability Repository ID is customfield_12414 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Vulnerability Repository Name is customfield_12415 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira INFO Tenable VPR Score is customfield_12416 (existing)
2021-10-13 13:38:31,421 tenable_jira.jira.Jira DEBUG Request: {"method": "GET", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/project/VMNGT", "params": {}, "body": {}}
2021-10-13 13:38:31,562 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "GET /rest/api/3/project/VMNGT HTTP/1.1" 200 None
2021-10-13 13:38:31,562 tenable_jira.jira.Jira DEBUG Request: {"method": "GET", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/issuetype/project", "params": {"projectId": "11338"}, "body": {}}
2021-10-13 13:38:31,687 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "GET /rest/api/3/issuetype/project?projectId=11338 HTTP/1.1" 200 None
2021-10-13 13:38:31,687 tenable_jira.transform.Tio2Jira DEBUG Issuetypes standard={'name': 'Task', 'jira_id': 3, 'type': 'standard', 'search': ['Tenable Plugin ID']}, subtask={'name': 'Sub-task', 'jira_id': 5, 'type': 'subtask', 'search': ['Tenable Platform', 'Tenable Plugin ID', 'Tenable Asset UUID', 'Device IPv4 Addresses', 'Device IPv6 Addresses', 'Vulnerability Port', 'Vulnerability Protocol']}
2021-10-13 13:38:31,687 tenable_jira.transform.Tio2Jira INFO Using JIRA Screens [11767, 11768]
2021-10-13 13:38:31,687 tenable_jira.jira.Jira DEBUG Request: {"method": "GET", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/screens/11767/tabs", "params": {}, "body": {}}
2021-10-13 13:38:31,812 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "GET /rest/api/3/screens/11767/tabs HTTP/1.1" 200 None
2021-10-13 13:38:31,812 tenable_jira.jira.Jira DEBUG Request: {"method": "GET", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/screens/11767/tabs/11913/fields", "params": {}, "body": {}}
2021-10-13 13:38:31,984 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "GET /rest/api/3/screens/11767/tabs/11913/fields HTTP/1.1" 200 None
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO CVEs already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Tenable VPR Score already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO CVSSv2 Base Score already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO CVSSv2 Temporal Score already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO CVSSv3 Base Score already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO CVSSv3 Temporal Score already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Tenable Plugin ID already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Tenable Plugin Family already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Tenable Plugin Name already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Vulnerability Severity already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Vulnerability First Seen already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Vulnerability Last Seen already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Vulnerability Last Fixed already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Vulnerability State already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Vulnerability Port already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Vulnerability Protocol already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Patch Publication Date already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.transform.Tio2Jira INFO Finding Severity already exists in 11767:11913
2021-10-13 13:38:31,984 tenable_jira.jira.Jira DEBUG Request: {"method": "GET", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/screens/11767/tabs/11914/fields", "params": {}, "body": {}}
2021-10-13 13:38:32,171 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "GET /rest/api/3/screens/11767/tabs/11914/fields HTTP/1.1" 200 None
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Tenable Asset UUID already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Tenable Asset Tags already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Tenable Platform already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Device Hostname already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Device NetBIOS Name already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Device DNS Name already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Device IPv4 Addresses already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Device IPv6 Addresses already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Device MAC Addresses already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Device Network ID already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Vulnerability Repository ID already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.transform.Tio2Jira INFO Vulnerability Repository Name already exists in 11767:11914
2021-10-13 13:38:32,171 tenable_jira.jira.Jira DEBUG Request: {"method": "GET", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/screens/11768/tabs", "params": {}, "body": {}}
2021-10-13 13:38:32,296 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "GET /rest/api/3/screens/11768/tabs HTTP/1.1" 200 None
2021-10-13 13:38:32,312 tenable_jira.jira.Jira DEBUG Request: {"method": "GET", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/screens/11768/tabs/11915/fields", "params": {}, "body": {}}
2021-10-13 13:38:32,484 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "GET /rest/api/3/screens/11768/tabs/11915/fields HTTP/1.1" 200 None
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO CVEs already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Tenable VPR Score already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO CVSSv2 Base Score already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO CVSSv2 Temporal Score already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO CVSSv3 Base Score already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO CVSSv3 Temporal Score already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Tenable Plugin ID already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Tenable Plugin Family already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Tenable Plugin Name already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Vulnerability Severity already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Vulnerability First Seen already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Vulnerability Last Seen already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Vulnerability Last Fixed already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Vulnerability State already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Vulnerability Port already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Vulnerability Protocol already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Patch Publication Date already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.transform.Tio2Jira INFO Finding Severity already exists in 11768:11915
2021-10-13 13:38:32,484 tenable_jira.jira.Jira DEBUG Request: {"method": "GET", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/screens/11768/tabs/11916/fields", "params": {}, "body": {}}
2021-10-13 13:38:32,640 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "GET /rest/api/3/screens/11768/tabs/11916/fields HTTP/1.1" 200 None
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Tenable Asset UUID already exists in 11768:11916
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Tenable Asset Tags already exists in 11768:11916
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Tenable Platform already exists in 11768:11916
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Device Hostname already exists in 11768:11916
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Device NetBIOS Name already exists in 11768:11916
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Device DNS Name already exists in 11768:11916
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Device IPv4 Addresses already exists in 11768:11916
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Device IPv6 Addresses already exists in 11768:11916
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Device MAC Addresses already exists in 11768:11916
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Device Network ID already exists in 11768:11916
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Vulnerability Repository ID already exists in 11768:11916
2021-10-13 13:38:32,655 tenable_jira.transform.Tio2Jira INFO Vulnerability Repository Name already exists in 11768:11916
2021-10-13 13:38:32,655 tenable.sc.TenableSC DEBUG {"method": "GET", "url": "https://<TENABLE_SC_HOST>:443/rest/query/2147?fields=filters", "params": {}, "body": {}}
2021-10-13 13:38:32,734 urllib3.connectionpool DEBUG https://<TENABLE_SC_HOST>:443 "GET /rest/query/2147?fields=filters HTTP/1.1" 200 404
2021-10-13 13:38:32,734 tenable.sc.TenableSC DEBUG {"method": "POST", "url": "https://<TENABLE_SC_HOST>:443/rest/analysis", "params": {}, "body": {"type": "vuln", "sourceType": "cumulative", "query": {"tool": "vulndetails", "type": "vuln", "filters": [{"filterName": "severity", "operator": "=", "value": [{"id": "1", "name": "Low", "description": "Low Severity"}, {"id": "2", "name": "Medium", "description": "Medium Severity"}, {"id": "3", "name": "High", "description": "High Severity"}, {"id": "4", "name": "Critical", "description": "Critical Severity"}]}, {"filterName": "lastSeen", "operator": "=", "value": "0-1634150312"}], "startOffset": 0, "endOffset": 1000}}}
2021-10-13 13:38:37,789 urllib3.connectionpool DEBUG https://<TENABLE_SC_HOST>:443 "POST /rest/analysis HTTP/1.1" 200 None
2021-10-13 13:38:37,914 tenable_jira.transform.Tio2Jira DEBUG Setting Vuln Sev to medium
2021-10-13 13:38:37,914 tenable_jira.transform.Tio2Jira DEBUG Setting Finding Sev to medium
2021-10-13 13:38:37,914 tenable_jira.jira.Jira DEBUG Request: {"method": "POST", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/search", "params": {}, "body": {"jql": "project = \"VMNGT\" and issuetype = \"Task\" and status not in (Closed, Done, Resolved) and \"Tenable Plugin ID\" ~ \"51192\""}}
2021-10-13 13:38:38,306 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "POST /rest/api/3/search HTTP/1.1" 200 None
2021-10-13 13:38:38,306 tenable_jira.jira.Jira DEBUG Request: {"method": "POST", "url": "https://<JIRA_CLOUD_HOST>/rest/api/3/issue", "params": {"update_history": false}, "body": {"fields": {"project": {"key": "VMNGT"}, "issuetype": {"id": 3}, "customfield_12390": "6.4", "customfield_12392": "6.5", "customfield_12394": "-1", "customfield_12395": "51192", "customfield_12396": "General", "customfield_12397": "SSL Certificate Cannot Be Trusted", "priority": {"id": "3"}, "customfield_12422": "Medium", "summary": "[51192] SSL Certificate Cannot Be Trusted", "description": {"version": 1, "type": "doc", "content": [{"type": "heading", "attrs": {"level": 1}, "content": [{"type": "text", "text": "Description"}]}, {"type": "paragraph", "content": [{"type": "text", "text": "The server's X.509 certificate cannot be trusted. This situation can occur in three different ways, in which the chain of trust can be broken, as stated below :\n\n - First, the top of the certificate chain sent by the server might not be descended from a known public certificate authority. This can occur either when the top of the chain is an unrecognized, self-signed certificate, or when intermediate certificates are missing that would connect the top of the certificate chain to a known public certificate authority.\n\n - Second, the certificate chain may contain a certificate that is not valid at the time of the scan. This can occur either when the scan occurs before one of the certificate's 'notBefore' dates, or after one of the certificate's 'notAfter' dates.\n\n - Third, the certificate chain may contain a signature that either didn't match the certificate's information or could not be verified. Bad signatures can be fixed by getting the certificate with the bad signature to be re-signed by its issuer. Signatures that could not be verified are the result of the certificate's issuer using a signing algorithm that Nessus either does not support or does not recognize.\n\nIf the remote host is a public host in production, any break in the chain makes it more difficult for users to verify the authenticity and identity of the web server. This could make it easier to carry out man-in-the-middle attacks against the remote host. "}]}, {"type": "heading", "attrs": {"level": 1}, "content": [{"type": "text", "text": "Solution"}]}, {"type": "paragraph", "content": [{"type": "text", "text": "Purchase or generate a proper SSL certificate for this service. "}]}]}}}}
2021-10-13 13:38:38,556 urllib3.connectionpool DEBUG https://<JIRA_CLOUD_HOST>:443 "POST /rest/api/3/issue?update_history=False HTTP/1.1" 400 None
2021-10-13 13:38:38,556 restfly.errors.BadRequestError ERROR [400: POST] https://<JIRA_CLOUD_HOST>/rest/api/3/issue?update_history=False body=b'{"errorMessages":[],"errors":{"customfield_12422":"Specify a valid \'id\' or \'name\' for Vulnerability Severity"}}'
2021-10-13 13:38:38,556 root ERROR Caught the following Exception
Traceback (most recent call last):
File "C:\Users\admin\AppData\Local\Programs\Python\Python39\lib\site-packages\tenable_jira\transform.py", line 407, in _process_open_vuln
i = self._jira.issues.upsert(fields=issue, jql=' and '.join(jql))
File "C:\Users\admin\AppData\Local\Programs\Python\Python39\lib\site-packages\tenable_jira\jira\issues.py", line 48, in upsert
issue = self.create(**kwargs)
File "C:\Users\admin\AppData\Local\Programs\Python\Python39\lib\site-packages\tenable_jira\jira\issues.py", line 18, in create
return self._api.post('issue',
File "C:\Users\admin\AppData\Local\Programs\Python\Python39\lib\site-packages\restfly\session.py", line 637, in post
return self._req('POST', path, **kwargs)
File "C:\Users\admin\AppData\Local\Programs\Python\Python39\lib\site-packages\restfly\session.py", line 543, in _req
raise error_resp
restfly.errors.BadRequestError: [400: POST] https://<JIRA_CLOUD_HOST>/rest/api/3/issue?update_history=False body=b'{"errorMessages":[],"errors":{"customfield_12422":"Specify a valid \'id\' or \'name\' for Vulnerability Severity"}}'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\admin\AppData\Local\Programs\Python\Python39\lib\site-packages\tenable_jira\cli.py", line 156, in cli
ingest.ingest(int(observed_since), first_discovery)
File "C:\Users\admin\AppData\Local\Programs\Python\Python39\lib\site-packages\tenable_jira\transform.py", line 749, in ingest
self.create_issues(vulns)
File "C:\Users\admin\AppData\Local\Programs\Python\Python39\lib\site-packages\tenable_jira\transform.py", line 527, in create_issues
self._process_open_vuln(v, fid)
File "C:\Users\admin\AppData\Local\Programs\Python\Python39\lib\site-packages\tenable_jira\transform.py", line 410, in _process_open_vuln
sys.exit(2)
SystemExit: 2
10898: Subtask
10738: Subtask
10742: Subtask
10813: Subtask
10760: Subtask
10942: Subtask
10892: Subtask
10901: Subtask
10746: Subtask
10784: Subtask
10883: Subtask
10866: Subtask
10861: Subtask
10928: Subtask
10832: Subtask
10920: Subtask
10763: Subtask
10800: Subtask
10924: Subtask
10960: Subtask
10933: Subtask
10776: Subtask
10936: Subtask
10841: Subtask
10880: Subtask
10889: Subtask
10957: Subtask
10916: Subtask
10952: Subtask
10874: Subtask
5: Sub-task
10807: Subtask
10735: Subtask
10757: Subtask
10810: Subtask
3: Task
10830: Task
10798: Task
10863: Task
10808: Task
10950: Task
10755: Task
10733: Task
10736: Task
10740: Task
10940: Task
10899: Task
10958: Task
10761: Task
10744: Task
10839: Task
10805: Task
10782: Task
10954: Task
10934: Task
10914: Task
10918: Task
10859: Task
10931: Task
10922: Task
10926: Task
10872: Task
10878: Task
10881: Task
10887: Task
10890: Task
10758: Task
@SteveMcGrath Do you have a script that will tear down everything, or should I do it manually? Didn't want to do it manually if there was an easier way.
You could try to just delete the "Vulnerability Severity" field and let the integration recreate and see if that fixes before going to far down the path of manually deleting everything.
Closing issue from lack of input
Error:
restfly.errors.BadRequestError: [400: PUT] https://<JIRA_CLOUD_HOST>/rest/api/3/issue/159483?notifyUsers=true&overrideScreenSecurity=false&overrideEditableFlag=false body=b'{"errorMessages":[],"errors":{"customfield_12422":"Field \'customfield_12422\' cannot be set. It is not on the appropriate screen, or unknown."}}'
I know this issue is typically fixed by https://github.com/tenable/integration-jira-cloud/issues/23#issuecomment-604631753, but this is happening even after I set my screens.
2021-09-30 16:23:28,381 tenable_jira.transform.Tio2Jira INFO Using JIRA Screens [11703, 11704]
I've double checked and those are the screen IDs for VULN: Task Management Create Issue Screen and VULN: Task Management Edit/View Issue Screen.
Any help is appreciated, thanks!
Debug: `### Configuration File:
Debug Logs
Available IssueTypes