This post explains the process used to design an Atlassian Forge app. The process is repeatable and will help ensure the app meets the requirements it needs to satisfy and will scale.

Atlassian provides insights into software development collaboration, project management, and team productivity, offering documentation, tutorials, and best practices for using Atlassian's suite of tools, including Jira, Confluence, and Bitbucket. By exploring Atlassian's curated content, developers can learn about agile methodologies, version control workflows, and continuous integration practices for managing software development projects effectively. Whether you're working in a small startup or a large enterprise, Atlassian offers resources to streamline your collaboration and drive project success.

Atlassian

A detailed walkthrough of designing a Forge app to manage internal F1 competition entries at Atlassian. The process starts with reverse-engineering requirements, identifying key abstractions (competitions, entries, users), and analyzing entity scaling needs. Two architectural approaches are compared: a traditional app with custom storage and access control versus leveraging Jira's native features (team-managed spaces, work items, custom fields). The Jira-based approach was chosen for better authorization handling and feature reuse, despite increased UI complexity. Key design considerations include Forge platform limits, entity property-based space designation, and restricting work item visibility to prevent users from seeing others' entries.

Designing a Forge app

Building the app utilising Jira abstractions