Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

Commit

Permalink
clarifying priority definitions (#2755)
Browse files Browse the repository at this point in the history
## Test Plans
not applicable -- handbook update
  • Loading branch information
ZrnH authored Mar 18, 2022
1 parent d5bffcd commit ad221b2
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ If you have gotten a specific feedback request that a customer(s) would like to

To create a Product Gap, navigate to the impacted customer(s) most recent Opportunity, whether it's a net new opp or a renewal. When viewing the Opportunity, you should see a related list labeled "Product Gap Submissions". Create a new Submission, and search in the field Product Gap to see if a gap already exists for what you wish to log. If no gap exists, create one, and then continue creating your submission that will tie your customer to the Product Gap. A gap submission should include the following:

- Severity - P0, P1, P2
- Severity - P0: Dealbreaker, P1: Significant Pain Point, P2: Nice to Have
- Use Case - _if relevant_ tie your submission to one or multiple core use cases to help with prioritization
- Description
- Impact
Expand Down

0 comments on commit ad221b2

Please sign in to comment.