-
Notifications
You must be signed in to change notification settings - Fork 988
Issue List Labels
We use labels to classify and categorize issues in this list & strive to classify every issue. Each label has a brief description explaining what it means. You can find those here: /SharePoint/sp-dev-docs/labels.
On this page, we provide a bit more information on specific labels.
When an issue has been tagged with Needs: Author Feedback, Needs: Context Detail, or Needs: Reproduce Steps and the original poster (OP) has responded to the thread, those labels are removed and this label is added. We use this to flag issues that "the OP was asked a question or for additional details and they responded."
This label is added to issues to indicate the OP of the issue needs to provide additional information or answer questions we've left for them.
If there's no response from the OP after a period of time, the no-recent-activity label is added by our bot. If there continues to be no response from the OP, the bot will automatically close the issue.
This label indicates we need additional context or details about the OP's scenario. Browser versions, installed software versions, target environment... the more information you provide the easier it is to help!
For more guidance, see the page How to create a good issue.
Similar to the Needs: Context Detail label, this label is used when we can't reproduce an error or problem the OP submitted. In those cases, we're asking for detailed steps to help us replicate the problem. If we can't replicate it, it is very hard to help.
For more guidance, see the page How to create a good issue.
Every issue added to the list gets this label. We use this label to identify new issues that have been submitted. Once we triage the issue by either addressing the topic and/or adding additional labels to classify it, we'll remove the triage label.
Having multiple issues open on the same root problem/bug/error results in a poor experience. This is true not just for the people trying to identify or work the problem as well as those monitoring the status of the issues. As such, if an issue is deemed to be a duplicate post of another issue, we will add a comment with the correct issue to use, add this label, and close the issue.
This label indicates Microsoft is tracking the issue in their internal systems. When there's an update to provide, they will provide one.
This label indicates your issue needs more detail. New issues contain a template with sections you should fill out. Each of these sections also contains some blockquoted sections with guidelines. If you didn't complete these sections, we'll classify your issue with this tag & include the Needs: Author Feedback label.
Before we can look at your issue, you need to finish submitting it. For more guidance, see the page How to create a good issue.
We recognize the issue may be a real problem, but unfortunately, there's not much we can do about it here. This repo is for SharePoint development and SharePoint developer issues. Anything outside that topic will get this label.
All capability question/discussion questions, or topics related to SharePoint administration & end-user topics should be reported through the support user interface available in the tenant admin settings. You can also have a discussion and ask questions at the SharePoint TechCommunity forum.
When we tag an issue with this label, the bot will leave a message explaining this and automatically close it.
As covered in the Issue List Overview page, feature requests don't belong in the issue list. They belong in the SharePoint Dev Platform UserVoice site so that we can take it into account in our future planning.
When we tag an issue with this label, the bot will leave a message explaining this and automatically close it.
-
Getting Started