← All case studies

Case Study

High-Density Forge Calendar for Jira Software & JSM

A Forge calendar I built end-to-end — backend, frontend, and Marketplace launch — that replaced the default Jira calendar's hard-coded limits with true hourly timelines, continuous multi-day spans, and overlap-safe layout at 1,000+ issues.

  • Forge
  • Jira
  • Marketplace
  • Scheduling
  • All events readable on busy days — no hidden "+ more" Day-density
  • Handles 1,000+ issues with batched fetching Scale
  • Productized and shipped on the Atlassian Marketplace Proof

Problem

  • Default Jira calendar hid events past three per day behind a "+ more" link, forcing repeated clicks on busy days.
  • No control over field mapping — start/end times, site/location, and visit type lived in custom fields the default view ignored.
  • No shared view that worked the same way across Jira Software and JSM projects.

What I built

  • Two-step fetch (keys → batched details) with buffered range loading for large datasets.
  • Overlap detection that lays out concurrent events without truncation.
  • Color-coded status categories, visit-type icons, legend, and site/location filters.

Stack

  • Atlassian Forge
  • Forge Custom UI (React)
  • Node.js (Forge resolvers)
  • Jira REST APIs + JQL
  • Jira Software & JSM

My role

  • Sole engineer — backend, frontend, admin UX, and Marketplace release
  • Architected a two-step fetch model (keys → batched details) to stay under Forge resolver limits
  • Built the React frontend with custom monthly and weekly views and overlap detection
  • Designed the admin panel for project selection and configurable custom field mapping

Security

  • Runs on Atlassian infrastructure (Forge)
  • Standardized resolver responses with retry/backoff
  • No external services — all data stays in Atlassian Cloud

Client details withheld under NDA. Built end-to-end while employed at a former Atlassian consultancy; IP belongs to that company.

Want something like this for your team?

Book a call →