Many companies manage their sales and customer sucess / client implementation in different tools, typically:
Sales and commercial account management in a CRM such as Salesforce, Hubspot or Pipedrive
Client implementation in a project management tool such as Jira or Trello

Often, this means sales people have to toggle between tools and / or spreadsheets to know what's going on on the implementation side. Or worst, they just don't know what's going on.

Let's see in this tutorial how to automatically compute some indicators from Jira at the client level and feed salesforce opportunities with that data.
Each issue in Jira is associated with a specific client, I have subtasks in each issue. I would like to count the number of subtasks per issue and feed that data to my opportunities in salesforce (each opportunity is associated with a client).

In video (without the sound unfortunately):

Start by importing your issues from Jira
In the field issue type, you have a field called subtask that tells you whether the issue is a subtask or not. Issuetype is a JSON, let's flatten it.
Now we can filter out the issues that are not subtasks, add a filter with the following formula:
Flatten status
Flatten status_statusCategory
Add the following filter:

Now, we need to be able to link each subtask to a specific opportunity in salesforce.
The name of our opportunities is the email of our client. Also, in Jira, we have a custom field for each issue called email_client with (surprisingly) the email of the client). But there is an additional difficulty, the email_client field is filled at the task level, but not the subtask level. But that won't be a problem!

Let's flatten the column parent.
We now have a column called parent_id, this is the id of the parent task of each subtask.
Let's make a second import of issues and let's rename it Issues_bis
Now, unfortunately, Jira doesn't give us the human name of custom fields but only the id. (to find the id of a custom field, check this out). In my case, the id of the custom field client_email is customfield_10028
If we check the field customfield_10028, we can see we have the email associated to each issue.
Now, let's go back to our first import. From then, let's use a vlookup to get the email associated to the parent of each subtask.

Vlookup to get custom field 10028 (=client_email)

Now that we have an email, we'll be able to deduce the id of the salesforce opportunity.
Let's import opportunities from salesforce
From our first Jira import, let's do a vlookup using the email as a matching key to get the opportunity id

Vlookup to get the opportunity id

We can do a pivot to calculate the number of subtasks with the status done for each opportunity id

Pivot to count the number of subtasks per opportunity id

Now, we're all set to push our data to salesforce
Click on Program actions, choose Salesforce / Update an opportunity
In id column, put id_opportunities
Now let's map our field in salesforce with our calculation in Actiondesk

Update opportunity in salesforce configuration

Finally, you can run once to see the result and schedule and publish your workflow at the frequency that's relevant for you.
Was this article helpful?
Thank you!