Idealite
← All case studies

{ Case Study }

Helping Atlassian Ship Confluence and Jira Changes With Confidence

On contract at Atlassian, Idealite led a frontend testing team whose Confluence and Jira work was proven before reaching customers.

{ Project Overview }

About the Project

Atlassian makes Confluence, a team workspace where knowledge and collaboration meet, and Jira, a project management tool that helps software, marketing, IT and operations teams plan, track and deliver work, from a single project to work spanning an entire organization. For Atlassian, a broken page or board can quickly reach many of the teams that rely on that product. That makes release quality a business concern, not only an engineering one: both products need to keep improving while customers' everyday work keeps running. On contract inside Atlassian's team, Idealite led the frontend testing team responsible for high-quality deliverables and worked directly in the core Confluence and Jira code. The team's tools included React, Playwright, Storybook and Bitbucket Pipelines.

Industry
  • Enterprise Software
Services

Frontend Test Leadership • End-to-End Testing • Team Augmentation • Pipeline Deployments

{ The Challenge }

Changing Products That Whole Organizations Rely On

Key Challenges

  • Whole organizations depend on Confluence and Jira
  • One faulty release can reach many teams
  • Improvements must ship without breaking workflows
  • Broken journeys must be caught early
  • Quality ownership without process disruption

{ Our Solution }

Quality Ownership Inside Atlassian's Own Team

  • Release-ready frontend work
  • Customer journeys checked pre-release
  • Protected customer workflows
  • Embedded testing leadership

{ How We Built It }

Development Process

How the Atlassian engagement came together, step by step.

  1. 01

    Join the Team

    Joined Atlassian's engineers on contract and worked directly in the core Confluence and Jira code, following Atlassian's own tools and processes.

  2. 02

    Own Release Quality

    Led the frontend testing team responsible for high-quality deliverables, making sure each piece of the team's work was ready before it shipped.

  3. 03

    Test What Customers Do

    Checked complete customer journeys end to end, and individual interface components on their own, so problems could surface before customers met them.

  4. 04

    Release With Confidence

    Shipped the team's tested work through Atlassian's own release pipeline, so improvements reached customers without bypassing quality checks.

{ Tools We Used }

Technology Stack

  • React
  • Playwright
  • Storybook
  • Bitbucket Pipelines

{ Results & Impact }

Delivering Business Value

Technical details

Requirements, architecture, development, testing and deployment notes.

Objectives

  • Protect Customer Experience: Keep Confluence and Jira working as customers expect while both products keep improving.
  • Raise Release Confidence: Hold the team's work to a high quality bar before it ships.
  • Catch Problems Early: Find broken screens and user journeys before customers run into them.
  • Strengthen the Team: Add frontend quality ownership without changing how Atlassian's teams already work.

Requirements

  • A contract role inside Atlassian's own team, codebase and processes
  • High-quality frontend React deliverables, tested before deployment
  • Unit, integration and end-to-end tests for the React frontend
  • End-to-end tests written in Playwright
  • Storybook for checking UI components in isolation
  • Changes in the core Confluence and Jira source code
  • Deployments through Bitbucket Pipelines after testing

Technology stack

  • React
  • Playwright
  • Storybook
  • Bitbucket Pipelines

Front end

  • React
  • Storybook

Testing

  • Unit tests
  • Integration tests
  • End-to-end (e2e) tests with Playwright
  • Storybook for checking UI component states in isolation

Deployment

  • Deployments through Bitbucket Pipelines, after testing

Challenges & solutions

  • From single teams to entire organizations, people rely on Confluence and Jira, so frontend changes must be proven before release.
  • Unit tests alone cannot show how components behave together or across a complete user flow, so integration tests and Playwright end-to-end tests covered those levels.
  • Changes land in each product's core source code, where a regression can reach the teams using it.
  • Inside the full product, UI components are hard to check state by state, so Storybook was used to check them on their own.
  • Releases must not bypass testing, so deployments through Bitbucket Pipelines followed testing.
  • In a contract role, Idealite had to fit into Atlassian's own codebase, tooling and processes.

Outcomes

  • Led a frontend testing team on contract inside Atlassian, responsible for high-quality Confluence and Jira deliverables
  • Tested the team's Confluence and Jira changes before release
  • Checked complete customer journeys end to end with Playwright, not just individual parts
  • Used Storybook to check interface components on their own
  • Contributed directly to the core Confluence and Jira code while working within Atlassian's own tools and processes

Next case study

Helping PokerBoss Get Players In and Keep Clubs Connected

{ Let's Build Together }

Let's build what's next

We partner with ambitious businesses to design, build and scale digital products that create lasting value.

Contact Us