Skip to main content

Integration between Komunikado - Salesforce® and Customer’s JIRA®

Client is going to implement “Komunikado”- Salesforce® and JIRA® connector to provide synchronization of tasks, subtasks, comments, worklogs in both directions between two JIRA instances via Salesforce.

Published by jetbi
18 August 2022
Salesforce

Project description 

Client is going to implement “Komunikado”- Salesforce® and JIRA® connector to provide synchronization of tasks, subtasks, comments, and work logs in both directions between two JIRA instances via Salesforce.

 

Goals and tasks 

  • Setup synchronization of tasks, subtasks, comments, and work logs between two JIRA instances;
  • Provide centralized analytics for JIRA issues completed for Account management
  • Implement SF Komunikado in the customer's business process;
  • Optimize current business processes of the customer;
  • Configure "Configure mapping settings" according to the data in the external and internal Jira;
  • Customize Salesforce CRM to meet unique customer needs.

 

Project scope 

The team performed consulting and development services including:

  • Registration of multiple connections for data migration;
  • Configured the transfer of data, such as tasks, subtasks, comments, and work logs;
  • Data migration in two directions, from external Jira to SF and from SF to internal Jira;
  • Migration of settings using the Data Loader;
  • Configuring fields in Issues, Comment, Worklogs section using mapping settings;
  • Configured the ability to view the status of data transfer for each connection.

 

Results 

  • SF Komunikado implemented and integrated into existing infrastructure;
  • Set up synchronization of data, such as tasks, subtasks, comments, and work logs;
  • Multiple connection registrations have been created;
  • Filters to transfer tasks in both directions from JIRA to SF and SF to JIRA were created; 
  • Filters for moving subtasks in both directions from JIRA to SF and SF to JIRA have been created;
  • Created filters to move work logs in both directions, from JIRA to SF and SF to JIRA;
  • Set up Configure mapping settings;
  • Configured processes to move tasks and subtasks in Schedule Synchronization from external JIRA to SF;
  • Configured processes to move tasks and subtasks in Schedule Synchronization from SF to internal JIRA;
  • Configured processes to move comments in Schedule Synchronization from external JIRA to SF; 
  • Configured processes for moving comments in Schedule Synchronization from SF to internal JIRA;
  • Processes have been set up to migrate the work logs in Schedule Synchronization from external JIRA to SF; 
  • Configured processes for moving work logs to Schedule Synchronization from SF to internal JIRA;
  • Configured ability to migrate/update data daily; 
  • Configured connectivity via JSON file; 
  • Configured ability to offload data from SF using JSON file;
  • Configured access encryption function in the uploaded JSON file.


Client's review:

"Thanks to Kommunikado implementation my team began to spend much less time logging tasks and describing work logs in two Jiras".

 

Start your project now
JET BI TEAM
  • 1 Salesforce developer
TECHNOLOGIES
  • Salesforce
  • JIRA
PROJECT TIMELINE
  • 1 day
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026