push_to_jira: fix pushing to JIRA during import/reimport in asynchronous mode

[valentijnscholten]

Findings weren't pushed to JIRA during import/reimport when postprocessing was happening in the background (default behaviour, unless block_execution was set to True). Bug was introduced in 2.53.0.

This was not caught by our unit tests as these run in synchronous mode.

During debugging I added some logging helpful for troubleshooting, let's leave that in place for now via this PR.

[dryrunsecurity]

This pull request logs the full DRF serializer context (which includes the request), causing request headers — including sensitive Authorization tokens like API keys or JWTs — to be written to debug logs. This could disclose secrets in logs and should be removed or redacted before logging.

Information Disclosure via Debug Logging in dojo/api_v2/serializers.py

Vulnerability	Information Disclosure via Debug Logging
Description	The code logs the entire context dictionary at the debug level. In a Django REST Framework (DRF) environment, this context typically contains the DRF request object. When the request object is converted to a string for logging, it includes all request headers, which results in the sensitive Authorization header (containing API keys or JWTs) being written to the application's debug logs.

django-DefectDojo/dojo/api_v2/serializers.py

Lines 2284 to 2287 in ec2c764

	logger.debug(f"process_scan called with context: {context}")
	start_time = time.perf_counter()
	importer = self.get_importer(**context)
	context["test"], _, _, _, _, _, _ = importer.process_scan(

---

All finding details can be found in the DryRun Security Dashboard.

[mtesauro]

Approved

added significant changes to the PR

[mtesauro]

Approved