Jira Edge Connect vs Ansible: Jira Automations Use Cases

Lance Waldrop

We have Ansible in our environment but are curious what uses might work better through Jira Edge Connect. Looking for any existing examples of common repeatable actions the community has in place.

Alexander Nilsson

Hello Lance,

great question - Ansible and Jira Edge Connector (JEC) overlap a bit, but they are used in different parts of the toolchain.​

High‑level positioning

• Ansible is best as your configuration management / orchestration engine: provisioning, patching, enforcing desired state, running complex multi‑step playbooks.​
• Jira Edge Connector is best as the bridge between Jira Service Management Cloud and things that live in your data center or private networks, especially when you want Jira Automation to trigger small, targeted scripts or call into existing tools.​

When to use JEC

• Run on‑prem scripts from Jira Automation
  Use the “Run script using Jira Edge Connector” action to kick off a script on a server that Jira Cloud cannot reach directly (inside your network / DMZ).​
  Examples: restart a single service, clear a cache, rotate a log file, call an internal HTTP API, etc.​
• Fast, targeted operations based on ticket data
  JEC can receive issue fields via environment variables / arguments and pass them straight to your script.​
  Examples:
  • Look up a CI or user in an internal DB/CMDB based on a custom field.​
  • Fetch extra diagnostics from a monitoring system and post them back as a comment.​
• Bridging tools that don’t have native Jira or Ansible integrations
  You can script against any CLI/HTTP API you have on that host, then push results back to Jira.​
  Examples: legacy ticketing/asset tools, home‑grown scripts, internal approval systems.​
• Tightly coupled ITSM workflows
  Because everything starts with Jira Automation, it’s easy to keep incidents / changes as the single source of truth, including status updates and comments from the scripts.​

Example automation use cases for JEC

• User / access provisioning
  • Trigger a JEC script on “Issue transitioned to Approved” in an onboarding / access request workflow.​
  • Script calls AD/LDAP or an internal IdM API to create the account, add groups, then writes results (username, system IDs) back to the issue.​
• Operational runbooks & remediation
  • For common incidents (disk full, service down, stuck process), a JEC script can execute the known remediation steps and update the ticket automatically.​
  • If remediation fails, it can attach diagnostic logs and bump priority / reassign.

• Monitoring / AIOps integration
  • Monitoring tool opens a Jira issue; on certain labels or priorities, an automation rule triggers a JEC script.​
  • Script enriches the ticket with metrics/logs or kicks off a downstream tool (e.g. Ansible playbook, Jenkins job).​
• CMDB / asset sync
  • When an asset‑related ticket is created/updated, call a JEC script to update your internal CMDB or asset system.​
  • Keep custom fields in Jira aligned with authoritative asset data.​

Where you should Ansible be used

• Complex multi‑host changes, rolling deployments, and idempotent infra changes.​
• Managing OS packages, services, and configuration at scale.​
• Anything that already lives in well‑tested playbooks and roles.

I am looking forward to your reply. 

If this solves your problem, feel free to mark it as Accepted so others can find it more easily.

Greetings

Alex