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

Steps following request submission

schema

icon

After receiving your request, we analyze it and we offer free online meeting slots (via email) so that we can discuss your needs in as much detail as possible

icon

We begin gathering all necessary requirements to create comprehensive estimates, including timelines, resource allocations, risk assessments, and underlying assumptions.

icon

Once all preparations are in place, we will initiate the project and move forward with the planned tasks