/
SiftScience[JIRA Cloud Integration with Salesforce]

SiftScience[JIRA Cloud Integration with Salesforce]

Owned by Sharmendra Vishwakarma
Last updated: Sept 02, 2020
3 min read

1. As-Is Process

Today Product uses Salesforce to track two objects related to customer requests:

  • Product Gaps, which are associated with a customer / prospect

  • Feature Requests, which group similar product gaps under one ask. Feature Requests have a status.

The main benefit of doing this in salesforce is that we can get customer account data (specifically name, churn risk, MRR, customer / prospect status) associated with a request

●     Otherwise, keeping requests in Salesforce is terrible: it’s very slow, filtering and searching are hard, and no one on Eng can see it (because Salesforce accounts are so expensive, only GTM have them)

2. To Be Process

  • Enable authorized users (i.e. PMs) to create a Jira issue from a Salesforce Feature Request record

  • Sync status from Jira issue to Salesforce Feature Request “Status” field

 

2.1 Process Flow

2.2 Requirements

Jira Issue Creation

If a PM decides to add a Feature Request to their team’s backlog, the PM will “promote” a feature request to a Jira issue (type Story). Ideally, the creation of the Jira issue happens in Salesforce. The ability to create the Jira issue from Salesforce is limited to authorized users only (PMs). Upon promotion of a Feature Request to a Jira issue, the Salesforce Feature Request record is automatically updated to point to the Issue. Similarly, the Issue points to the Feature Request. The Feature Request record status is automatically set to Backlogged in Salesforce.

The Feature Summary field in the Feature Request record is copied to the Jira issue Description field.

The new Jira field “Customer visible” is set to TRUE.

 

2.3 Technical Developments

2.3.1 Changes to SFDC Feature Request record

 

Field / button name

Purpose

Change to...

Jira issue

Link to Jira issue

New field

Create Jira issue

Creates a new Jira story issue, pre-populated with information from the SFDC record

New button

 

2.3.2 Changes in Jira Issue

Field / button name

Purpose

Changes

Feature Request

Link to Salesforce Feature Request record

New field

Customer visible

Flag to identify issues that are a customer-impacting change

New field

 

2.3.3 Events

 

Application

Event

Action

Application

Event

Action

1

Salesforce

Promote feature request to issue

●   Creates a new Jira issue (type: Story)

●   Copies Feature Request/Feature Summary field to Story/Description field

●   Sets Feature Request status to Backlogged

  • Sets Jira issue field Customer Visible to TRUE

2

JIRA

Story assigned to sprint

Salesforce Feature Request status set to Planned

3

JIRA

Story status set to In Progress

Salesforce Feature Request status set to Building

4

JIRA

Story status moves from
In Progress to Closed

Salesforce Feature Request status set to Released

 

 

2.3.4 Jira Issue States Transitions

 

Process Step

Current State

Next State

State Pushed to SFDC

Process Step

Current State

Next State

State Pushed to SFDC

1

PM or Eng creates Jira issue

Jira issue created from FR (state == AwaitingFeedback OR Backlogged)

Open

  • PM Review

  • In Review

  • Closed

FR → Backlogged

2

PM or Eng moves to PM Review

PM Review

  • In Review

  • Closed

  • In Review: None

  • Closed : FR → Declined

3

PM or Eng moves to In Review

In Review

  • Issue assigned to sprint

  • Closed

  • Issue assigned to sprint : FR → Planned

  • Closed : FR → Declined

4

PM or Eng assigns Issue to sprint

Unchanged

In Progress

FR → Building

5

PM or Eng moves to In Progress

In Progress

Closed: done

Closed: won’t fix

Closed: done : FR → Released

Closed: won’t fix : FR → Declined

6

PM or Eng moves to Closed

Closed

None

None

 

2.3.5 Data

SFDC Status (PickList)

Name

Description

Name

Description

1

None

Defaulted

2

Awaiting Feedback

 

3

Planned

 

4

Building

 

5

Released

 

6

Declined

 

7

Backlogged

 

 

3. Scope

3.1 In-Scope

 

3.2 Out of Scope

 

3. Approach

  • On Click of create button on SFDC , Issue gets created in Jira under the defined Project

  • Use Skyrocket plugin and configure in SFDC and Jira Cloud

4. Work Breakdown Structure (WBS)

 

Sl No

Task

Description

Estimated Effort(Hours)

Sl No

Task

Description

Estimated Effort(Hours)

1

Configuration of SFDC

 

 

2

Configuration of Jira Cloud

 

 

3

Integration Testing

 

 

4

UAT

 

40

5

Hyper-Care

 

40

5. Dependency

 

 

6. Glossary