Summary

Enable Jira Edge Connector (JEC) functionality for non-JSM Jira projects to allow secure integration with internal services without requiring public endpoints.

Currently, JEC is only available for Jira Service Management (JSM) projects, forcing Jira Software/Business users to either:

1. Create public endpoints for internal services (security concern)

1. Use a complex workaround involving JSM Premium/Enterprise licenses on the same site that involves using a Global Automation rule.

1. Restructure their architecture to accommodate cloud-only webhook limitations

This limitation is particularly challenging for organizations that:

• Recently migrated from on-premise Jira installations

• Have internal services behind firewalls

• Need to integrate with internal databases and logging systems

• Cannot expose internal services to the public internet for security reasons

Current Behavior

• JEC action appears in Automation rules for JSM projects and Global Automation rules if you have at least a JSM free license.

• If you have a JSM Free plan, when attempting to configure JEC, users receive an error that "API key cannot be created"

• The JSM restriction is not clearly communicated in the UI (only mentioned in documentation)

• This creates a frustrating user experience where the feature appears available but fails silently

Proposed Solution

Enable JEC functionality for Jira Software projects, allowing:

• Creation and management of JEC API keys for Software projects

• Full access to JEC actions in Automation rules

• Secure communication with internal services behind firewalls

Use Cases

1. Internal Database Lookups

• Retrieve incident data from internal logging systems using incident IDs from custom fields

• Process large JSON responses that may exceed current Automation limits (16KB for Enterprise)

• Attach retrieved data as JSON files to issues (workaround for size limitations)

2. Legacy System Integration

• Connect with on-premise systems that cannot be exposed publicly

• Maintain existing integrations during cloud migration

• Preserve security policies that prohibit public endpoints

3. Internal Tool Automation

• Trigger internal build systems

• Update internal tracking databases

• Synchronize with proprietary internal tools

Workaround:

Currently there is a workaround for using JEC with software projects if you have a JSM premium or enterprise license in the same site. If you do, you can create a global automation rule, add the JEC action there and then use the rule with your software project.

Current workaround requires:

• JSM Premium/Enterprise license on the same site

• Creating global automation rules in JSM

• Not viable for organizations with JSM on different sites

• Adds unnecessary complexity and licensing costs