Koppla - External References for Jira

Jira Project: Koppla Individual Event Source Configuration screen
Jira Issue: Tab when no matching data is found using Koppla

Inspiration

Just like many organizations, we have a lot of issues in Jira. And just like these other organizations, we have related information stored in a variety of other systems that aren't tightly integrated with Atlassian Jira. With Koppla, we can make this external system data visible inside our Jira issues. Having access to the data we need - when and where we need it - enables collaboration and improves decision-making.

What it does

Koppla allows the project administrator to define one or more event sources inside a project. For each event source , the admin designates a Jira issue field that will contain a value used to find information relevant to a Jira issue in the external system. A utility developer can then submit a snippet of the remote data to Koppla's database.

Whenever the Jira issue is rendered, Koppla searches the database for the relevant information related to the key field value and shows any relevant data it finds to the Jira issue viewer. Worried about security? No fear, the project administrator controls who can see the data from each event source, making it possible to control who can see what on each issue.

How we built it

This is built using Atlassian Forge storage API, FaaS, and a react front end (using Custom UI).

Challenges we ran into

The storage API restricts how much we can store. We would love to be able to store more data, however due to the pagination and not being able to search data properly - we're limited to 32K per issue value.