RaceOps

RaceOps is a real time race operations platform built on Atlassian tools that unifies live engineering issues, strategy decisions, and session reports into a single source of truth for Formula one.

Comment

Inspiration

Formula One race operations happen under extreme time pressure, where every decision can change the outcome of a race. We were inspired by how race engineers, strategists, and analysts collaborate in real time and wondered how the same clarity and structure could be brought into digital workflows. Atlassian tools are already central to team collaboration, so RaceOps was born to bridge high-pressure motorsport decision making with Jira-powered execution.

What it does

RaceOps is a Jira dashboard gadget that acts as a real-time race operations overview. It provides a central, always-visible space where teams can understand the purpose of RaceOps, align on race-critical objectives, and contextualize decision making during Practice, Qualifying, and Race sessions. The dashboard is designed to reduce context switching and keep everyone focused during high-intensity moments.

How we built it

RaceOps was built using Atlassian Forge and implemented as a Jira Dashboard Gadget using UI Kit, which is fully supported in Jira dashboards. The app is defined through a Forge manifest and deployed directly into a Jira Cloud instance. By using UI Kit components, we ensured the gadget renders reliably within Jira’s dashboard environment while staying lightweight and performant.

Challenges we ran into

One of the biggest challenges was understanding the strict limitations of Jira dashboard gadgets. Dashboard rendering does not support arbitrary React or HTML, which required us to rethink our approach and switch from Custom UI to UI Kit. We also navigated Forge configuration issues, resolver structure, and deployment edge cases before arriving at a stable, dashboard-compatible solution.

Accomplishments that we're proud of

We successfully built and deployed a Forge app that integrates cleanly into Jira dashboards and clearly communicates a real-world use case inspired by Formula One race operations. We’re proud of translating a high-pressure, real-time collaboration problem into a focused Atlassian-native solution that fits naturally into existing workflows.

What we learned

We gained a deep understanding of Atlassian Forge, especially the differences between UI Kit and Custom UI and where each is appropriate. We also learned the importance of aligning product design with platform constraints and how small architectural decisions can have a big impact on stability and usability.

What's next for RaceOps

Next, we plan to extend RaceOps with dynamic Jira data such as live issue counts, race-session tagging, and deeper integration with Confluence for post-session reporting. Long-term, RaceOps could evolve into a full operational command center for motorsport teams, combining live telemetry insights with structured task tracking and decision logs.

Share this project:

Updates