Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update surfacing_product_feedback.md #4869

Closed
wants to merge 2 commits into from
Closed

Update surfacing_product_feedback.md #4869

wants to merge 2 commits into from

Conversation

ZrnH
Copy link
Contributor

@ZrnH ZrnH commented Sep 29, 2021

No description provided.

@sourcegraph-bot
Copy link
Contributor

sourcegraph-bot commented Sep 29, 2021

Notifying subscribers in CODENOTIFY files for diff 546ce28...9e3f9eb.

Notify File(s)
@christinaforney handbook/product/surfacing_product_feedback.md

@ghost ghost self-assigned this Sep 30, 2021
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One typo, a few comments to take or leave.


## When to create a GitHub issue
To create a Product Gap, navigate to the impacted customer(s) Account and whatever current open Opportunity they have, whether it's a net new opp or a renewal. When vieing 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. Be sure to include relevant information like what workarounds your customer must employ (if any), and the severity of what this issue blocks for them.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a big deal but should it be "most recent open opportunity they have"?

vieing => viewing

"and search in the field Product Gap, to see if a Gap already exists for what you wish to log"
I don't think you need a comma after Product Gap

inconsistent capitalization of gap on its own, probably capitalize Product Gap, but not gap

@ghost ghost assigned ZrnH and unassigned ghost Sep 30, 2021
@ZrnH ZrnH closed this Sep 30, 2021
@ZrnH ZrnH deleted the ZrnH-patch-1 branch September 30, 2021 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants