/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

After acquiring Code Barrel in Oct., Atlassian launches native no-code automation across Jira Cloud products with support for Slack, Microsoft Teams, and others

A few months ago, Atlassian acquired Code Barrel, the Sydney-based company behind the popular Automation for Jira low-code tool for …

TechCrunch Frederic Lardinois

Context & Ripple Effects

This launch closes the loop on Atlassian's October 2019 purchase of Sydney-based Code Barrel, whose Automation for Jira tool had already been adopted by Visa, Cisco, and Airbnb. Rather than keeping it a paid marketplace add-on, Atlassian has folded the engine natively into Jira Cloud and extended its triggers beyond Jira itself to Slack, Microsoft Teams, and other tools.

The move follows the same playbook as the $425M Trello acquisition: buy a proven capability, then distribute it through Atlassian's installed base. It also set up the surface that Atlassian Intelligence would later land on three years down the arc.

First-order effects

  • Jira Cloud admins get automation rules built in at no separate procurement step, displacing the standalone Automation for Jira app and any rival rule-builder plugins in the Atlassian Marketplace.

Second-order effects

  • By wiring Jira events directly into Slack and Microsoft Teams, Atlassian pulls automation out of developer tooling and into the chat surfaces where non-engineers work — putting pressure on those platforms' own workflow features and on integration vendors like Zapier whose value was connecting exactly these apps.

Third-order effects

  • If acquired capabilities keep getting absorbed into the core cloud subscription, the Atlassian Marketplace shifts from a revenue channel toward a scouting pipeline, and buyers increasingly evaluate suites on built-in automation rather than per-tool purchases.

The trend: Collaboration-software vendors are consolidating point-solution automation tools into their own clouds, making cross-app workflow orchestration a bundled feature rather than a product category.