Connecting CRM and JIRA with nFeed

Connecting your CRM and JIRA with nFeed

There are many CRM softwares that can help companies to keep track of their contacts, such as SAP, Microsoft Dynamics… However, such tools show limitations when combined with JIRA. Indeed, the information stored in those databases are constantly updated and have to be imported into JIRA. In the past, the only way to do this was by re-creating all the data into JIRA, which was a long process and did not provide data synchronisation.

Today all your troubles are over, I’ll share with you my experience of this limitation and show you a quick and easy way to synchronise information.

JIRA and your CRM, two independant tools

At Valiantys, we manage our clients and contracts information through SAP, but this use case could be implemented with any other CRM: Sugar CRM, iRise, Microsoft Dynamics…

On the other hand, our company provides a support service through which our clients can raise tickets and bugs. Thus, our developers use JIRA to maintain our products and JIRA Service Desk is used as our support desk. In order to be efficient, we have created “companies”  in JIRA in which each employee is a JIRA user and can raise tickets.

At the beginning, it was impossible to identify which users were linked to which company and contracts. We aimed at having different SLAs depending on the information, but JIRA was not able to do that.



Here is the thing: on the left, there is SAP gathering all the information related to the clients (contracts, contacts …) and on the right, JIRA and Service Desk in which clients raise tickets. These two parts have no link. This is where nFeed comes into action and can make the task much easier.


Here is a list of the specific information I want to appear in my issues:

  • Company information : company name, address and phone number
  • Main contact information: his/her name, email and phone number
  • Contract information:  the contact related to this client is the start and end date of the contract

In Salesforce, I have the detail of employees working in each company, thus, I will check the reporter in JIRA  and associate all the client information depending on this field.


Let’s take a look at my JIRA environment now.

As you can see, I’ve got a customer portal without any configuration.

Customer Portal

I raise a ticket from this portal with the user “Aude”.

Aude issue

The reporter is “Aude” and I configured three tabs on the view screen to display the information from Salesforce. These fields are in Read-Only mode because I don’t want them to be changed in JIRA. The first tab gathers the Company Information, the second tab contains the employee information and the last one has the contract information.

Now, let’s see the impact of creating another ticket with the user “Test” on JIRA.

Test issue

The reporter is “Test” and the Company information matches the reporter (NFeed). The information in these three tabs are different depending on the reporter, as requested. If I want to change the field reporter, for example from “Aude” to “Test”, the client information will also change automatically.

In our configuration we get information from the reporter field, although you can also use another field (e.g. assignee, custom fields …) to get data from SAP. 

To conclude…

Data management is vital for a firm, so don’t let anything get in your way! If you experiencing the limitations of a combined use of JIRA and SAP, nFeed will help you synchronising data and overcome them. And if you’re still hesitating, try it for free and make your own opinion about it!



Cutted Triangle

Subscribe to the Valiantys Newsletter

Registered request ! Subscribing... This is not an email An error occured

In accordance with our privacy policy, we are committed to respecting your personal data.

Contact us

Our Atlassian certified consultants will be happy to answer you.

Join us

We're building the next dream team - Are you in?

Follow us

We use cookies for the operation of our website. This is to improve its use, to personalize your experience, and to compile visitor statistics. By continuing to use this site, you consent to this policy. You can manage the settings and choose whether or not to accept certain cookies whilst browsing. For more information, see our privacy policy. Our privacy policy

Privacy settings

In order to facilitate your navigation and to provide you with the best possible service, we use cookies to improve the site to the needs of our visitors, particularly according to the number of visitors. For more information, please read our privacy policy. Our privacy policy


Google reCAPTCHA is a system designed to distinguish humans from computers, so that bots are unable to maliciously fill out forms on behalf of a human being.


Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. Used by the social sharing platform AddThis to store the user's usage history of the AddThis sharing widget. Registers a unique ID that is used to generate statistical data on how the visitor uses the website.


Targeting Cookies: Targeting cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant advertising on other sites. They are based on uniquely identifying your browser and internet device. You can turn off the use of cookies for targeted advertising here. When the button is green, targeted cookies are on. When the button is red, targeting cookies have been turned off.

Social Media Cookies: These cookies are set by a range of social media services that we have added to the site to enable you to share our content with your friends and networks. They are capable of tracking your browser across other sites and building up a profile of your interests. This may impact the content and messages you see on other websites you visit. If you do not allow these cookies you may not be able to use or see these sharing tools.