Issue tracker

• 

Inspiration

The idea for this project came from my early experience using Jira for issue tracking during learning and practice projects. While Jira is powerful, I noticed that switching between multiple views to understand issue context often breaks focus. I wanted to build a lightweight solution that keeps essential issue-related information accessible directly within the issue view, improving clarity without adding complexity.

This project was also motivated by my desire to learn Atlassian Forge and understand how production-grade apps are built and deployed on the Atlassian platform.

What it does

This project is a Forge-powered Jira app that enhances issue tracking by embedding a dedicated panel directly within the Jira issue view. It allows users to access and interact with issue-related information without leaving the issue page, reducing context switching and improving workflow efficiency.

The app integrates seamlessly with Jira’s existing interface and follows Atlassian’s design and security guidelines. By operating entirely within Jira, it ensures a smooth and intuitive user experience while keeping performance lightweight.

How we built it

The project was built using Atlassian Forge, leveraging its serverless runtime and UI framework. The core steps included:

Defining the app structure and Jira module placement in manifest.yml

Implementing the UI logic using Forge UI components

Testing the app locally and in the development environment

Iterating based on behavior observed inside real Jira issue pages

Deploying the final version to the production environment

Installing and validating the app on a live Jira site

The app is designed to be minimal, fast, and intuitive, ensuring it integrates naturally into Jira’s existing workflow without disrupting users.

Challenges we ran into

One of the main challenges was understanding where and how Forge apps appear inside Jira, as certain modules only render in specific contexts (such as issue pages). Another challenge involved managing environments correctly and ensuring the production version behaved identically to the development version.

Additionally, configuring permissions correctly while keeping them minimal required careful attention to Atlassian’s security guidelines.

Overcoming these challenges significantly strengthened my understanding of real-world cloud app deployment and platform-based development.

Accomplishments that we're proud of

Successfully built and deployed a production-ready Forge app

Implemented a Jira issue panel that renders reliably in the correct context

Managed multiple environments (development and production) without breaking functionality

Completed the full lifecycle: development → deployment → installation → verification

Followed least-privilege permissions and platform security best practices

Gained hands-on experience with real-world cloud app deployment

Ensured the app is reviewer-friendly, easy to test, and well-documented

What we learned

Through this project, I gained hands-on experience with:

Atlassian Forge platform and its cloud-native architecture

Writing and validating manifest.yml configurations

Understanding Jira modules such as issue panels and UI extensions

Managing development, staging, and production environments

Deploying, installing, and upgrading Forge apps

Atlassian’s app security model, permissions, and scopes

I also learned how reviewers and users interact with apps differently depending on the environment, which helped me design the app with clarity and accessibility in mind.

What's next for Issue tracker

Next, Issue Tracker will focus on improving usability, adding customizable issue details, and enhancing performance. Future updates aim to provide better configuration options and richer issue context while staying lightweight and fully integrated within Jira.

Built With

• forge