Sidekick4All is NOW available on the Atlassian Marketplace

View on Atlassian Marketplace

About the project

Inspiration

Across marketing, sales, HR, support, and legal teams, we kept seeing the same problem:

Work is planned in Jira, but it happens in calendars.

Meetings consume time that is never logged, while Jira tasks lack protected focus time. This leads to misalignment, inaccurate reporting, and slow decision-making across teams.

We built Sidekick4All Connecting Teams Across Jira and Calendars to reduce this gap and connect the two worlds where work really happens.


What it does

Sidekick4All connects teams by synchronizing Jira and Google or Microsoft calendars in both directions:

  • Jira issues create calendar focus blocks to protect time for work
  • Calendar meetings are automatically captured as Jira worklogs
  • Planned time and actual effort stay aligned
  • Manual timesheets and follow-ups are no longer required

This gives business teams clarity and speed by aligning what is planned with what actually happens.


How we built it

Sidekick4All is built as a Forge-native Atlassian app designed to feel like a natural extension of Jira rather than an external integration.

Key building blocks include:

  • Jira issue events to detect when work should be scheduled
  • Forge UI for configuration and team preferences
  • Secure Forge storage to manage calendar links and synchronization state
  • Event-driven workflows that translate Jira updates into calendar actions and calendar events into Jira worklogs

By relying on Forge, we avoided external infrastructure and ensured security, performance, and compliance with Atlassian Cloud best practices.


Challenges we faced

The main challenge was handling bi-directional synchronization without creating noise or conflicts.

Key challenges included:

  • Preventing duplicate calendar events and Jira worklogs
  • Respecting personal and team calendars without being intrusive
  • Balancing automation with user control
  • Designing workflows that work for business teams, not just developers

We addressed these challenges through careful event handling, clear ownership rules, and thoughtful defaults.


What we learned

Building Sidekick4All showed us that productivity problems are rarely caused by missing tools. They are caused by misaligned systems.

We learned that:

  • Business teams need automation that works quietly in the background
  • Calendars are a critical but underused source of truth
  • Forge enables powerful, secure, event-driven apps without operational overhead
  • Small reductions in friction can have a large impact on team alignment

What's next

Sidekick4All is just the beginning. Planned next steps include:

  • Capacity management to help teams understand availability and avoid overload
  • Shareable scheduling links that align Jira work with real calendar availability
  • Rovo agents with multiple actions to proactively schedule focus time and capture work across Jira and calendars

Our goal is simple: help teams stay aligned across Jira and calendars, where work really happens.

Built With

  • atlassian-forge
  • custom-ui
  • forge-sql
  • google-calendar-api
  • jira-cloud
  • jira-entity-properties
  • microsoft-graph-api
  • nodejs-22
  • oauth-2-0
  • react
  • serverless
  • typescript
  • vite
Share this project:

Updates