Announcing: Jira integration made easy with the Jira connector

By Phil Burch

Make Jira integration easy for Slack, GitHub, Salesforce, and many other tools

Citizen automators, welcome to Jira integration made easy! The Tray.io team is excited to announce the launch of a powerful new connector for Jira, the popular project tracking platform that many world-class product and engineering teams already use to document progress, issues, and bugs for their software development projects.

What does this mean for you? Now, your product and engineering teams can use a full-featured Jira integration to connect their outstanding tickets, boards, and sprints with the rest of the applications in their tech stack. In addition, other teams can now benefit from instant visibility into project status updates by using a Jira integration into other systems of record, such as your CRM.

What you can do with the Tray Platform’s Jira integration

The Tray Platform’s native Jira connector is robust and offers many useful operations to help your product teams document their software development faster while also efficiently syncing updates with other, related teams. Of course, the Tray Platform offers support for almost all API operators and our intrepid connector team is always adding more. The Jira connector offers such operations as:

  • Create issue - Create a new issue
  • Create issue attachment - Create an attachment to an issue
  • Create issue comment - Create a comment on an issue
  • Create issue link - Create a link between two issues
  • Create version - Create a project version to be released
  • Delete issue - Delete an issue from your Jira account (and optionally delete attached subtasks)
  • Get comment property - Return the value of a comment property
  • Get issue - Return the details of an issue
  • Get user - Get a specific Jira user
  • Get user info - Return information about the current Jira user
  • Get version - Get a project version by ID
  • List board sprints - List all sprints for a specific board
  • List boards - List all boards
  • List issue comments - List all comments for an issue
  • List issue worklogs - Return all worklogs for an issue
  • List project issues - List all issues in a project
  • List projects - List all projects visible for the current user
  • List sprint issues - List all issues in a specific sprint
  • Search issues (JQL) - Search issues using Jira Query Language
  • Search users - Return a list of users matching a search string
  • Search users (Jira server) - Return a list of users matching a search string for a Jira server instance
  • Transition issue - Change the status of an issue
  • Update issue - Update an issue
  • Update version - Update a project version

As a reminder, in addition to the native connector’s various operations, you can also build out any additional functionality using the Tray Toolkit for universal connectivity.

Next, some specific use case examples for Jira integration.

Example #1: Jira Slack integration/Jira Microsoft Teams integration

While many engineering teams are used to working within Jira to update and manage tickets, it can also be useful to get direct Jira updates in other channels. Fortunately, you can build a Jira Slack integration or a Jira Microsoft Teams integration in the Tray Platform to trigger alerts and notifications within the popular messaging programs Slack or Microsoft Teams. This type of integration can be useful not only to send alerts to product and engineering team members via Slack or Microsoft Teams, but also to provide visibility on Jira status updates to teams who are less active with Jira, such as revenue teams. Here is a basic example for the sake of discussion:

Jira Slack integration

In this automated workflow, we use a Jira Slack integration (or a Jira Microsoft Teams integration) to make quick updates to Jira tickets directly via chat, which product teams can access with a “/” slash command or a built-out panel in Slack or Microsoft Teams. Our workflow then routes the inputs from Slack/Microsoft Teams to Jira by looking up the issue in question, updating it, and returning a confirmation message via Slack/Microsoft Teams to the end user.

You can imagine extended use cases of a Jira Slack integration/Jira Microsoft Teams integration that involve distributing cross-team chat notifications, or calendar-based metrics-focused alerts for engineering managers that deliver reports on overall percentage completion of ticket or sprint status. There are plenty of possibilities here!

Example #2: Jira GitHub integration

Another use for Jira integration might be connecting Jira to GitHub, the popular open-source software hosting hub. For instance, you can use a Jira GitHub integration to directly sync Github code requests with the related issues and/or sprints in Jira. For the sake of discussion, here is another simple example of a workflow in the Tray Platform that updates your Jira instance by auto-creating tickets whenever you create new GitHub issues:

Jira GitHub integration

We kick off the initial trigger for this workflow using a GitHub-based trigger. In this case, our trigger initiates whenever someone creates a new GitHub issue. The workflow then performs a quick Boolean (true/false) loop to avoid creating duplicate Jira tickets. Specifically, our Boolean determines whether a ticket that corresponds to the new GitHub issue already exists within Jira. If the Boolean loop is “true” (that is, no ticket corresponding to the new GitHub issue’s ID exists), our workflow then auto-creates a corresponding new Jira ticket.

Obviously, this is an extremely simplified example, but you can imagine other use cases for a Jira GitHub integration, such as auto-syncing comments from various projects between GitHub and Jira, or auto-documenting version history within Jira tickets whenever GitHub users commit a new version of code.

Example #3: Salesforce Jira integration

Another potential use case for Jira integration is a Salesforce Jira integration. Salesforce is, of course, a popular CRM (customer relations management) platform that revenue teams, particularly sales, use as a system of record for prospect accounts, ongoing sales deals, and lead records. Using the Tray Platform’s connector for Jira integration, you can build a Salesforce Jira integration workflow that syncs the project tracker’s data with your CRM. We can go over a basic example here in which we auto-update the account record for a major customer account with status updates on mission-critical projects:

Jira Salesforce integration

We kick off this workflow with a Jira trigger, which listens for any updates to a major project which our product and engineering teams are building for a top-tier customer account. Since our customer has an extremely valuable account, we take a white-glove approach to this customer’s requests.

As it turns out, while the customer is currently happy, it has requested a major custom buildout that requires our engineering team to properly scope and develop it over the course of several weeks (or months). Over the course of the project, as the engineering team helps scope out the work then gets development underway, the product team dutifully updates the project in Jira. Our workflow auto-syncs the details of any updates in Jira into Salesforce to populate a custom field in our CRM that documents project progress. Other teams that use Salesforce, including the customer success team, can get progress reports directly from our CRM to keep the customer updated - without the need for endless engineering/product/customer team meetings to sync up.

Take Jira integration for a spin

By now, you should have at least a few ideas of how you can use the Jira connector in the Tray Platform to build your own custom Jira integration to the services you use every day. If you’re already a Tray.io customer, what are you waiting for? Log in to the Tray Platform to get started.

Get additional Jira Integration ideas in this video now:

Otherwise, get more inspiration and real-world examples of using automation and integrations for Jira and other important tools you use every day by joining a weekly group demo.