Vercel DevOps for Jira

Connect Vercel deployments to Jira issues and give a clear view of what was deployed, when and why.

Comment

Inspiration

The app was inspired by a visibility gap between deployment activity in Vercel and delivery tracking in Jira. Deployments were happening frequently, but the connection to Jira issues stopped at the commit message in the Git repository. I wanted both project managers and developers to see the same source of truth: which Jira issues actually went out with which deployment. By automatically linking Vercel deployments to Jira issues, the app makes delivery status explicit, shared, and reliable across roles.

What it does

The app manages relationships between Vercel projects and Jira projects. As soon as a Vercel project is deployed (production, staging, development), the app processes the deployment information and tries to identify any Jira issues related to the deployment. Then, the deployment information is submitted to Jira and can be seen in the development tab when viewing a Jira issue or on the project's development overview. This helps project managers keeping an overview on the different deployments and related issues.

How we built it

  • Atlassian Forge for building the app
  • Vercel's REST API for retrieving deployment and project information
  • Jira's DevOps REST API & the new Teamwork Graph Connector to provide deployment information from Vercel to Jira

Challenges we ran into

I spent some time figuring out how I should set the values for the deployment information so that they make sense for other users when they view it in Jira. Also, thinking about a way how people might want to configure the connection to Vercel and relationships between Vercel projects and Jira took some time and is still not perfect. And unfortunately, a few days before the submit deadline I ran into a problem of having duplicated deployment information as can be seen in the video. It's not clear to me why it happens and needs to be investigated again.

Accomplishments that we're proud of

The app supports providing API tokens within its own UI or by using the new Teamwork Graph Connector. Having both means the app is prepared for the future where Teamwork Graph is the essential source of truth for Atlassian systems.

What we learned

Creating a video and presenting the most important features is not easy and takes time 😀

What's next for Vercel DevOps for Jira

I want to learn from other users which information they're missing because eventually I want to publish the app to the Atlassian marketplace. Also, additional capabilities are on my list, like a Forge Automation Action to trigger certain actions from Jira in Vercel for re-deploying a project or retrieving additional data.

Built With

Share this project:

Updates