Contacts

Komunikado Application Version 1.4: Improved Data Processing

About Us
Published by jetbi
03 August 2023
68

Komunikado App is used for data synchronization between Jira® and Salesforce® organizations. The main advantage of this application is the ability to automate the processing of a large amount of data, as well as to set the daily execution of these processes at a certain time of the day. 

There are some important improvements that are implemented in version 1.4 of the Komunikado App:

  • Added the check box “BREAK AFTER ERROR” to the schedule synchronization page.
  • The process of handling mass records has been improved, and more informative descriptions for error messages have been added to the synchronization history.
  • Added the ability to use any type of field to upload data from JIRA.

Let’s take a closer look at the updates and their advantages:

1. Breaking processes after error now can be controlled. A "Break After Error" checkbox has been added to the schedule synchronization page. If this checkbox is active, then after an error occurs, the entire data transfer process will be immediately stopped in the "error" status. The user can view the error message by clicking on the "Synchronization history" button. If the checkbox is not active, then the data transfer will not be broken after an error occurs.

 

2. Mass data records handling improved. Now if a user needs to send a lot of records to JIRA®, he no longer needs to worry that one error will break the whole process. After this improvement, all entries from the scope will be processed anyway. And the errors that occur will be collected and published in the synchronization history row.

 

3. Added availability to map a Picklist Salesforce field with any JIRA® field. In previous versions, a user could use only a restricted set as a field type (String, Date, Datetime, Double, Integer), but when he needs to map any field with Picklist, it’s never populated after synchronization. Now it is possible.

 

Also, users can configure a set of available field types using Custom Setting “JIRA® Object Types”.

 

Thus, the updates in the current version are designed to improve the process of automatic processing of a large number of records. Previously, the Komunikado application was used with the expectation that there would be no errors in the process that could interrupt the operation. Now, a much more convenient error-handling mechanism has been implemented to eliminate their recurrence. 


Get a Komunikado demo and use this application for faster processing of a large amount of data in JIRA®.

Aleksandr Zherebilo
Certified Salesforce Developer
image
Expertise
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