We're trying to integrate InsightIDR with Jira Service Management Cloud using the Extension Library workflow "Create Issue in Jira from IDR Investigation" (v2.0.0), but we're running into two issues.
Environment
InsightConnect (Automation) + InsightIDR (SIEM) on the Insight Platform
Jira Service Management Cloud
Jira plugin installed: v6.7.1 (the workflow lists v6.5.3)
No orchestrator connections configured
Issue 1 – Workflow import does nothing
Steps to reproduce:
Workflows → Add Workflow → Browse Templates
Open "Create Issue in Jira from IDR Investigation" (v2.0.0)
Click Import
Expected: the import wizard opens (plugins / connections / parameters). Actual: nothing happens. No wizard, no error message, and the workflow does not appear in Workflows (checked both Active and Inactive filters).
Issue 2 – Jira cloud connection is not visible after creation
We created a Jira cloud connection (Settings → Plugins & Tools → Connections → Add Connection → Jira → Cloud, using URL + email + API token). We got the success message: "Jira has been successfully created. Please note that cloud connections will not be visible in the connections page."
The Connections page shows "No connections yet". We understand from the docs that cloud connections are managed from the workflow builder and Quick Actions, but Jira is not available in Quick Actions, so we have no way to view, edit or test the connection to confirm it actually works.
What we've tried
Importing from both extensions.rapid7.com and Browse Templates inside InsightConnect
Looking for the .icon file in the Extension Source link (GitHub), but couldn't find it ther
Our goal is simply to automatically create a Jira Service Management ticket for each InsightIDR investigation/alert. Any guidance on how to get this working, or on the recommended approach for this use case, would be greatly appreciated.
I just tested importing this workflow, and everything worked as expected on my end.
I'd recommend clearing your browser cache and trying the import again. If the issue persists, please open a Support case, as this is not expected behavior.
Jira Plugin Connections
The cloud connection is shared across minor versions of the same major plugin version. For example:
Version 6.5 and 6.7: Use the same connection.
Version 7.x: Requires a new connection because it's a new major version.
How to Access the Jira Connection Manager
If you need to view or manage your existing Jira connection, you can access it through a snippet:
Navigate to the Workflows tab.
Select Snippets.
Create a new Jira snippet.
Add or select any Jira action within the snippet.
From that action, you can access the Jira Connection Manager.
This allows you to view and manage your Jira connections without needing to modify an existing workflow.
Unfortunately the issue persists. Here's what we found after clearing the browser cache:
With my user: clicking Import still does nothing (no wizard, no error, workflow not created).
With another user in the same organization: the import created the workflow, but it was empty (0 steps, 0 plugins) with the error "workflow does not have a trigger", so it couldn't be activated.
After deleting that empty workflow and retrying with the same user: the import does nothing again.
Since the behavior varies depending on the user, we suspect it could be related to permissions/roles or to the deleted workflow, but we're not sure. We'll open a Support case as you suggested and will post the solution here once it's resolved.
About the Snippet tip: it worked great, thanks! Through the Jira Connection Manager I was able to see our cloud connections, and found a surprise: there were 4 Jira cloud connections, 2 working and 2 failing. I fixed the failing ones and now all 4 are up, but I'd like to keep only one connection. However, I can't find an option to delete cloud connections from the Connection Manager.
Is it possible to delete a Jira cloud connection? If so, how?
Thanks also for clarifying that the cloud connection is shared across minor plugin versions, that was very helpful.
I fought this same issue for nearly three months. Support was engaged, escalated, escalated again, and then escalated some more. Each round delivered the same predictable responses with little meaningful progress.
Eventually, after making enough noise and refusing to let the issue disappear into the support abyss, they finally corrected the code and fixed my session. Victory, right? Not quite. The global variable still doesn't update properly, which means I still can't reliably track and close the associated tickets.
At this point, my frustration goes well beyond this one issue. Updates routinely break existing workflows, menus change every time I log in, and I can't even remove unwanted applications from my subscription. It's becoming increasingly difficult to maintain reliable security operations when the platform itself keeps moving the goalposts.
I've spent more time troubleshooting the tools than actually using them to improve security. That's a problem.
My advice? Keep the pressure on your CSA, document every failure, and don't accept another generic support response as a resolution. Persistence seems to be the only escalation path that actually produces results.