Skip to main content

Komunikado as a real time saver for Salesforce

About Us
Published by jetbi
24 March 2022
29

Many companies that use Salesforce and Atlassian JIRA in their work face a number of issues related to time logging by employees, data is not entered into both systems at the same time, forgetfulness, and simply doing it untimely and of poor quality. And also employees spend a lot of effort on logging and start to feel uncomfortable because of this.

In this article JET BI's Project manager and Salesforce consultant describes how critical pain points could be solved by the JET BI internal product. 

Management as a discipline includes a large list of managers' functionality. One of the main goals of management implies a constant efficiency increase and consequently provides improvement of economic, production, organizational and financial efficiency, which results in business growth and the achievement of financial goals.

One of the key processes in management is control, while this function can take up to 40% of the total working time spent. The issue of monitoring the efficiency of working time used by employees is quite acute, especially in 2020 after the transfer of many employees to remote work. To solve this problem, various methods and tools are used by managers by controlling the time spent by employees. But different interacting companies may use a wide range of applications controlling working hours, and such a method could be inefficient when an employee fills out reports on the work done. Actually, it could lead to the fact that the employee will have to fill out different forms for recording working hours twice or more times overall, in the contractor's company and in the customer's company, that determines the question of using working hours effectiveness by the employee.

To solve this issue, JET BI proposed a solution as a connector between SalesForce and Atlassian JIRA accounting programs, named  “Komunikado”. 

Thus, the Komunikado product helps to reduce the amount of time used for recording working hours, transferring tasks and logs from one accounting system to another.

In this article, I’d like to propose a number of figures that were obtained during the study of the problem within the JET BI company.

On average, an employee spends up to 30 minutes a day logging time in one accounting system. However, the process of transferring tasks, logs, messages to another accounting system doubles the time and it could reach 60 minutes per day, which could reach 10.5 hours according to the results of research during the month. Imagine that at the end of the year this figure could be 126 working hours, paid to the employee by the employer. Now you can easily calculate the load for the company if a team of 2, 3, 5, or more employees work on such projects. Economic efficiency falls, profit from the project decreases, costs rise*

As for technical features:

- synchronization in both directions of records from Salesforce® to Atlassian JIRA® issues, comments, attachments, a full log of data sync for audit and troubleshooting, 100% Force.com® native managed package;

- flexible configuration of field and object mapping, custom objects and fields support;

- independent scheduling and mapping for each Atlassian JIRA® Project\Salesforce® Object.

As for advantages:

- increased team productivity, for this point, as an example was given an internal survey at JET BI;

- software licenses cost efficiency;

- fully native on Force.com®;

- fast and secure implementation;

- customizable for unique needs.

Thus, we see that the Komunikado product is a universal connector between two common software environments used by many organizations, its installation, and usage help to optimize and reduce the use of working time for logging, which decreases costs both in the short and long term.

Komunikado will be available on AppExchange.in the nearest future. Stay tuned!


Evgeniy Klukach
Project Manager
image
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