Chargebee Jira Service Deck Connector

Inspiration

Our organisation has recently switched to using Chargebee to manage subscriptions for Confluence Server product licenses.

We were thinking that allowing Jira service desk agents to quickly view the subscriptions that a customer has will help them in deciding how to proceed with a ticket.

What it does

After connecting with Chargebee, there will be a panel in Service Desk projects displaying Chargebee customer details, monthly recurring revenue (MRR), as well as active and in trial subscription that the customer has.

How we built it

We built it using Ruby on Rails for the backend.

For the frontend, we utilised React as we want to make use of the Atlaskit components.

Challenges we ran into

We were going to use the reporter's email to search for the corresponding customer in Chargebee.

For that information, we require the Jira Email API, which requires a ticket to be raised to Atlassian with some 'ready for production' information, which we unfortunately do not have yet.

https://community.developer.atlassian.com/t/guidelines-for-requesting-access-to-email-address/27603

For now, we have hardcoded the email used to pull the Chargebee customer information.

What's next for Chargebee Jira Service Deck Connector

We are hoping to give it slightly more polish and get it to Marketplace, as well as work on getting approval for the email API.

We are considering to implement a search function, that will allow for service desk agents to search for the company that the reporter is part of. We are aware that a ticket reporter might not be the same contact in Chargebee.

Built With

• atlaskit
• react
• ruby-on-rails