Application Integration, Linking, and Jira Ecosystem
Connecting Jira to the outside
Integration covers application links, webhooks, REST API, issue linking, and marketplace apps. Application links establish trust between Jira and another application (often another Atlassian product) and enable features like shared user directories or cross-product linking. Webhooks push event payloads to an external URL when issues change. The REST API allows programmatic read/write and is the backbone of most integrations.
Issue linking connects issues with typed link types (blocks, relates to, duplicates). Link types are global and can be customized; a link is directional in meaning but visible from both issues. Remote links connect an issue to an external URL or object.
Traps to watch
- Confusing an application link (trust between apps) with a webhook (outbound event push).
- Assuming a webhook retries indefinitely; failed deliveries may be dropped after retries.
- Forgetting that link types are global configuration, not per-project.
- Overlooking that marketplace apps can add fields, workflows, and permissions that interact with core configuration.
Rule of thumb
Ask "is this inbound trust, outbound notification, or a relationship between issues?" Application link = trust; webhook = outbound event; issue link = relationship.
Worked example: an external system must be told whenever a high-priority issue is created. Use a webhook (or automation with a web request) triggered on issue creation with a JQL condition, rather than an application link, which is for trust between applications.