10. Requirement & Scope

As-IS

1. Today Product uses Salesforce to track 2 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.

2. 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

3. 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)

Goal

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

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

Workflow

Open

Process

Jira Story 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 Story, 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.

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.

Sprint Planning

Once the R&D team assigns the issue to a sprint, the Salesforce Feature Request status is automatically updated to Planned.

Sprint Execution

When the R&D team changes the Issue state to In Progress, the Salesforce Feature Request status is automatically updated to Building.

Done

When the R&D team is done with the work and marks the Issue state Closed, the Salesforce Feature Request status is automatically updated to Released.

Requirements

This section summarizes required changes to the Jira issue and Salesforce Feature Request record, as well as the integration between the two tools.

Changes to SFDC Feature Request record

Changes to Jira issue

Events

*Note: Check the feature, Moving the status on SFDC once Story is assigned to a Spring