Labeling schema

Label	Resolution details
Area: XXX	Identifies area of Office development (for determining who to assign an issue to). Areas may be added as needed, and each area will have an assigned owner on the DevX team.​ -Add-in areas: Dialog API, Excel, Word, General Runtime, others TBD -Graph areas: Auth, SDKs, Graph Explorer, others TBD​.
Blocker	This issue prevents the use of the API, technique, or sample​.
Bug: Documentation	This issue describes a bug in published documentation or samples, which has been logged internally​.
Bug: Product	This issue describes a bug in a Microsoft product or service, which the response coordinator has logged internally​.
Bug: Sample	This issue describes a bug in a published sample, which the response coordinator has logged internally​.
By Design	This item is working as intended (this category is a subset of Won’t Fix)​.
Duplicate	This issue has already been reported elsewhere; if possible, should provide a response that links to the original issue​.
External	This issue is not directly related to Office Extensibility / Calc org’s responsibilities (e.g., an Edge bug)​.
Fixed	This issue has been addressed and resolved (should also be closed in GitHub UI)​.
Fun	Not a critical need, but addressing it may be fun/interesting​​.
Help Wanted	This is an interesting and possibly useful idea which the community could help with as an open source contribution​​.
High Impact	Issue that affects many use cases or makes a dramatic difference in perf/usability/etc​.
Loc – localization issue	Identified by loc suppliers or response coordinator​​.
Needs More Info	A response has been posted asking the original poster for clarification; waiting on their response​. Follow-up in a week, if no answer, then comment and close issue.
Not Actionable This issue is not actionable, so no action will be taken​​.
Question	This is a question, and the response coordinator is tracking down an answer​.
Request: Documentation	This is a request for new documentation, which the DevX team may take into consideration​
Request: Feature	This is a request for a new feature, which the engineering team may take into consideration​
Request: Sample	This is a request for a specific sample, which the DevX team may take into consideration​
Resolved: Awaiting Validation	A fix has been made (and is available in an alpha/beta release). However, we’re asking the original poster to validate that this indeed fixes their issue. Use this for the less-straightforward or customer-environment-specific bugs].
Resolved: Awaiting Prod Deployment	A fix has been made in Alpha/Beta, and is queued up for Production, but Production itself has not yet deployed.​
Simple	Resolving the issue will require minimal work; use to search for “low-hanging fruit” that can be addressed quickly​ and close.
Stack Overflow	Resolve by referring customer to Stack Overflow. Use boilerplate in comment: "Could you please post this question in Stack Overflow and tag your question with office-js? This repository a good forum for receiving technical support on the API itself. This forum is specifically for errors/issues with the documentation set rather than the API itself. While there is certainly overlap, questions regarding the use of the library should be posted on Stack Overflow where you'll likely get a quicker response and benefit other developers facing the same challenges. Be sure an include a complete description of your problem and the code you're using to make the call. Without enough detail the community won't be able to provide any guidance." Close after referring customer to SO.
Under Investigation	Response coordinator (or a person they’ve reached to internally) is looking into this item.​
Won’t Fix	Issue has been researched and no action will be taken (a friendly explanation of the reason should be provided)​.