The Jira integration is dormant until Venvera enables the platform Jira OAuth application. Until then authorizing Jira returns a "not configured" error.
Unlike the cloud posture scanners, the Jira integration is a task sync, not a compliance scanner, so it produces no findings. It lets you push a Venvera task into Jira Cloud as an issue and keep the two linked.
What it does
When you push a task to Jira, Venvera creates a Jira issue and records the link back on the task (the external system, id, and URL) so you can jump straight to it. The new issue is labelled from the task's framework and type plus a venvera label, making Venvera-originated work easy to filter in Jira. Connecting uses a 3-legged OAuth flow with Atlassian; the encrypted tokens and your Jira cloud id are stored against your organisation.