Merge branch 'dbg-update-sm-support-request-details' into 'master'

added clarity on when an issue is committed to.

See merge request gitlab-com/www-gitlab-com!37049

source/handbook/marketing/product-marketing/index.html.md

@@ -128,8 +128,8 @@ All Strategic Marketing Work is tracked and managed as issues in the Strategic M
 **Strategic marketing request review and assignment flow** (note: the label `sm_request` indicates a request for Strategic Marketing support)  
 1. **New requests** start with the label `sm_req::new_request`.
    1. **Triaged** to one of the Strategic Marketing teams (PMM,TMM, Competitive Intell, Partner Marketing, Market Research/Cust Insight) `sm_req::triage` and the team label (`pmm`,`tech-pmm`,`Competitive Intelligence`, `Partner Marketing`, `mrci`) who will determine if if there is enough detail to prioritize and plan the work - is it clear?   Then the issue will be route to either:
-   1. **Backlog** `sm_req::backlog` for future scheduling, sequencing, and implementation.  *note: add issue to the SM_Backlog milestone for tracking.*
-   1. **Assigned** `sm_req::assigned` to team members.   When an issue is assigned, it is added to the quarter **milestone** so we can track status of all the work in flight.
+   1. **Backlog** `sm_req::backlog` for future scheduling, sequencing, and implementation.  *note: add issue to the SM_Backlog milestone for tracking.* **NOTE: Issues in the backlog are NOT yet committed to be done!**
+   1. **Assigned** `sm_req::assigned` to team members.   When an issue is assigned, it is added to the quarter **milestone** so we can track status of all the work in flight. **NOTE: Assigned issues should be considered committed to be done!**
    1. *Transferred* `sm_req::transferred` for requests that belong in a different team (Field Marketing, Sales, Ops, etc). Once an issue is transferred, it should be **closed**
    1. *declined* `sm_req::declined` - when an issue is in the backlog and it is no longer relevant or does not make sense anymore.  **Close** the issue when you *decline* it.
 1. When **complete**, the team member will update the issue with `sm_req::completed` and **Close** the issue