Issue Analytics for Jira

Track who's viewing your issues and turn that into valuable insights

Comment

Inspiration

Throughout our years of experience with project management and Jira, one major problem we encountered was that people often complained about not knowing if their well-structured, clear, and open Jira tickets were getting the attention they needed after creation. We want to contribute to resolving the root cause of unread tickets and improve tracking of ticket engagement. Our goal is to increase trust and collaboration between teams.

What it does

Each time an issue is opened, our app logs it and allows you to turn it into valuable insights. It lets you see the last viewers and also provides the possibility to check how many times they viewed the issue and when. It also facilitates understanding the unique views, which means how many different people saw the issue, as well as the total views.

How we built it

We integrated the latest technologies that Atlassian offers. Our app is written in TypeScript, built on top of the Atlassian Forge platform using its Custom UI to extend the UI capabilities while mostly sticking with Atlaskit to maintain consistency between Jira and our app. This allows us to benefit from responsiveness, dark theme options, and localization. We also used Forge storage to securely keep the view logs and maintain the data.

Challenges we ran into

Starting with Forge was so easy that we initially spent a significant amount of time deciding how to structure our code to keep the app scalable and versatile, allowing us to welcome new features in the future.

Accomplishments that we're proud of

  • We are proud that our app runs entirely on Atlassian, ensuring that your sensitive data never leaves your instance and allowing you to benefit from the data residency options Atlassian offers.
  • We started building this for Codegeist, but it turned out so well and we had such enthusiasm that we took a step further and submitted it to the Marketplace. Now it's our first app, proudly displayed in the Marketplace.

What we learned

  • Forge greatly facilitates most of the boilerplate tasks and lets us focus solely on the code.
  • We also had a more philosophical realization: App development is not just points of achievement in time, but a continuous, iterative flow with milestones.

What's next for Issue Analytics for Jira

We are actively working to improve our app. Our roadmap includes:

  • Adding gadgets that will help visualize view data per issue and per person.
  • Developing a Rovo agent that will analyze the correlation between the views of a ticket and its quality (e.g., clear description or missing acceptance criteria), compare them with other issues' data, and suggest improvements to the ticket reporter for their future tickets.
  • Checking if users mentioned in comments or issue descriptions have viewed the work item after being mentioned.
Share this project:

Updates