Connect

4 min read

3 real-life use cases on how to get external data into Jira

Alternative Text
Written by Cécile Sablayrolles

Jira is a powerful tool: it is great for planning, tracking, and managing projects. But sometimes it doesn’t allow you to do exactly what you or your clients want.

Has this ever happened to you? You are at a kick-off meeting with a new client to gather his needs. At some point, he mentions his sales team is using Salesforce CRM to manage all their accounts: “Oh wouldn’t it be great if we could get information from Salesforce accounts into Jira? We just paid a lot to get Salesforce, and we really need to capitalize on the investment. If we are paying for lots of services that don’t work together, that’s no good. We can do it, right?”

This is one of the multitude of requests a client can make for retrieving and gathering external data to input into Jira Software or Jira Service Desk.

Fortunately the answer you can give him is “Yes, of course we can! And I know exactly which tool you need to do that!”

Elements Connect (formerly nFeed) brings your external data inside Jira custom fields. It works with an extensive range of external data sources.

To present the variety of use cases implementable with Elements Connect, we created a demo portal. We have selected for you 3 real-life use cases you may face some day (or have already faced) as a Jira consultant or Jira admin, from suggesting similar issues to retrieving details from a CRM or LDAP.

Retrieve data about clients from Salesforce CRM

The situation

A company is using side by side Salesforce for managing their customer accounts and a Jira Service Desk portal for customer support.

The goal

To improve customer support, it is useful to provide agents with additional information about customers raising requests from the Jira Service Desk portal. The goal is to provide details about the client directly in Jira Service Desk, such as name, job title, phone, his or her Salesforce account and related opportunities, and to make this information only visible by the agents. This way they will have more context  and can better answer requests.

How Connect can help

With Elements Connect, you can add different custom fields to your Jira Service Desk request form and only display them on the agent side.

These fields are connected to Salesforce using the Salesforce connector, and Elements Connect fetches the requested data remotely from Salesforce to populate these fields. You get exactly the data you are looking for depending on the selected client. In this case, the fields are populated with the client details (name, job title, phone and email address), the associated Salesforce account and the related opportunities.

Integrating Salesforce data in Jira with Elements Connect

Get employees details from LDAP into Jira

The situation

A consulting company is gathering all employees details (phone, email, manager name, organization, etc.) within LDAP.

For this company, Jira is the main tool for project management. It is used by HR teams for onboarding processes, marketing teams for managing campaigns, and consulting teams for resources allocation & planning. For these teams, a great benefit would be to access employees information into Jira.

The goal

Get employee information from LDAP and display it in Jira so Jira users have access to relevant employees information in context.

How Connect can help

In this example, Elements Connect can get specific information about the current user (his name, job position, phone number & email address) by executing LDAP queries on the company’s LDAP.

All this data is nicely displayed in a user card using some HTML, providing the task’s assignee all the information he or she needs about the employee.

Elements Connect Jira LDAP integration

Present similar issues to avoid duplicate issue creation in Jira Service Desk

The situation

A software company is using a Jira Service Desk for managing issue & bug requests on their products.

Using Jira Service Desk for retrieving and managing customers requests is a common thing for customer-focused software companies. However if a bug is detected and reported by a customer, other customers are probably facing the same issue and are likely to raise it too. That leads to duplicated tickets, which are difficult to manage by the agents.

The goal

To avoid the creation of duplicate issues in Jira Service Desk, by informing the customer of existing similar issues upon issue creation.

How Connect can help

An additional field “Similar issues” can be added to the Jira Service Desk request form with Elements Connect. This read-only field is connected to the local Jira, and lists existing issues with a similar summary.

When the customer begins to type his or her request in the Summary field, a dynamic JQL query is executed based on what is typed in the Summary field to display issues that have a similar summary in the Connect “Similar issues” field. This way, the customer is directly informed about the existing similar issues, can take a look at them if needed and watch the one corresponding to his or her problem until resolution.

Make Jira work with any external data source

It’s common for consultants to work with clients who have multiple different tools. The risk with this diversity of solutions is to lose time looking for information in various sources and even data duplication. With Jira and Elements Connect, you can make these tools work together, gather all information into Jira and make your clients’ lives easier.

Interested in implementing one of these use cases? You can download the configuration of each example from our Elements Connect demo portal and try them on your own Jira instances.

You can also find a lot of other examples with various data sources and learn how to connect to knowledge bases, product catalogs, translation tools, and more.

To access to it, you just need to create an account. Have a look and get inspired!

And next time you meet a client who wants to connect Jira to Salesforce or any other data source, you’ll know what to do!