Contacts

Komunikado release. New features and opportunities to save time

About Us
Published by jetbi
30 November 2022
93

Many companies that use Salesforce and Atlassian JIRA in their work face a number of issues related to time logging by employees, data not entered into both systems at the same time, forgetfulness, and simply doing it untimely and of poor quality. Employees also put a lot of effort when logging in and start to feel uncomfortable because of this. Kommunikado is a tool to solve that issue. As already described in the article, Komunikado is a product that allows you to save resources and acts as a connector between Salesforce and Atlassian JIRA accounting programs, which in turn leads to a significant reduction in time spent.

Now, we propose to consider what innovations appeared in the updated version of Komunikado. Here are the new following features:

  • Counter of synchronized records;
  • Quick editing of matching records on SF object;
  • Authorization in JIRA in two modes: with Tempo and without it;
  • Implemented transfer of work logs from Jira with and without Tempo.

 

Let's take a closer look at the information about the new functionality:

  • Implemented a counter of the synced records which are transferred by the Komunikado app.  An administrator can set a max number of records to sync, and he can give premium (unlimited) access to the app.

komunikado-new-release-1

 

 

  • Implemented the mapping records viewing after the page initialization. If you need to edit some mapped records on any SF object, now you don’t need to set all of them, just edit them and click the “Save” button.

komunikado-new-release-2

 

  • Implemented JIRA authorization in 2 mods: with Tempo and without Tempo. The default mode is without Tempo, where you need credentials from Jira only. In this case, worklogs will be transferred with Jira API only. If you set “Use Tempo” as true, you can transfer worklogs with Tempo API and log time as the other users.

komunikado-new-release-3

 

  • Implemented worklogs transfer from Jira with JIRA API. It allows extracting worklogs from any Jira which has no Tempo App.
  • Updated worklogs transfer to JIRA, implemented 2 mods: with Tempo API and with JIRA API. Tempo mode now uses Tempo API v4.0, to transfer worklogs that were extracted from another Jira without Tempo. And you can transfer worklogs to Jira without Tempo, but all time will be logged on the current authorized user.

 

As you can see, the product keeps on going and getting more useful and convenient for users. So as a result, the Komunikado release was improved by JETBI Team and now can bring more value to customers using it. If you are interested in please contact us via email or contact form.

Evgeniy Klyukach
Project Manager
image
Expertise
Question to the expert
profile
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
Clutch: 4.9 out of 5 stars

We design and deliver business intelligence solutions to the most complicated challenges of the world’s biggest companies.
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
Read more
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
Read more
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
Read more