Table of contents

Introduction

Elements Connect is the go-to app to connect Jira fields to any data source. As such, it's a powerful tool that you can use to accomplish many use cases.

The examples you'll find here will help you get up to speed quickly with its configuration. They range from basic use cases such as the filtered issue picker to more advanced configurations like the Best Buy catalog searcher. 

While our goal is to make Elements Connect easy to configure, it requires some efforts to be fully mastered. Our selection of popular configurations is here to guide you on your journey learning how you can use Elements Connect. 

Examples are grouped by data source. Each of them contains a short demo, an explanation on how it has been implemented and a direct link to download the field configuration so you can try it on your own instance.

 Don't know which use case you should start with?
Have a look at the Elements Connect demo portal where they are all implemented .

Local Jira instance

Use case	Description	Demo	Complexity
Filtered issue picker	An issue picker that only lists issues matching a predefined JQL filter	link
Similar issues	Display issues matching the current issue summary; the similar issues list is updated as the user types.  It allows to prevent the creation of duplicate issues.	link
Fields missing in JSD	Some Jira fields are not natively available on Jira Service Desk: Group picker Project Picker but, they can be implemented with Elements Connect.	link

Remote Jira

Use case	Description	Demo	Complexity
Remote issue picker	To reference "something" that is listed as an issue in a project of another Jira. It can be an existing bug, a user story, etc.	link
Remote project component & version picker	Cross reference components / versions of between Jira project on remote instances.	link

User directory

Use case	Description	Demo	Complexity
LDAP	Get user information from a LDAP (phone, email, manager name, organization, etc.) Automatically fetch data about the current user.	link

Finance

Use case	Description	Demo	Complexity
Live exchange rate	This is particularly useful for teams managing quotes, proposals or costs in Jira and dealing with multiple currencies.	link
Stock

CRM

Use case	Description	Demo	Complexity
Salesforce	Use these fields to provide agents with additional information about customers raising request from a Jira Service Desk portal. The information can be made only visible by the agents.	link

Knowledge base

Use case	Description	Demo	Complexity
Suggest Confluence articles related to Summary	Suggest relevant knowledge base articles in live when a customer is about to create an issue. It's quite similar to what Jira Service Desk natively offers, but with Elements Connect you can go much further: Here the CQL query used to get the articles can be fine-tuned and it's possible to get pages from many spaces. It's also possible to connect to any KB system (given it offers a REST API or you have access to its database)	link
Suggest Atlassian Community posts related to Summary	Dynamically list Atlassian Community articles matching the content of the "Summary" field Suggest relevant knowledge base articles live when a customer is about to create an issue.	link

Product catalog

Use case	Description	Demo	Complexity
Best buy	Build a product catalog browser connected to Best Buy REST API Let your user select: a product category a product and see the product information in a read only field	link

Translation

Use case	Description	Demo	Complexity
Deepl	What it does Field 1: Display the translation of the content of the description field. Field 2: Indicates the language in which the description is written. Use case When a user inputs the issue description in a foreign language, automatically translate it to english to ensure agents understand the request. How it works Elements connect fields are connected to the Deepl REST API.	link