Have no idea what it is. Please confirm that this is obsolete.
This items directly related to money. Do not allowed on the triage phase.
Following "Do not make prioritization decisions" rule this is forbidden.
Following "Do not make prioritization decisions" rule this is forbidden.
Anything shipping releated is not allowed I believe.
Triagers cannot make decision about porting I believe.
Teams for large projects.
Large themes for work. Set by appopriate folks.
Resolution for the issues most likely should be set not by triagers.
I think this is allowed, but possible no longer needed and areas are wierd.
Too much identical statuses. Triagers need guidance on how to proceed.
Processor architecture on which issue appears.
Operation system where issue occurs.
All API should follow standard acceptance process.
Features classificaiton helps with routing to appropriate dev.
Have no idea what it is. Please confirm that this is obsolete.
Have no idea what it is. Please confirm that this is obsolete.
I assume this is merge statuses for PR automation tools in dotnet repo.
I would like to know about history of this classificaiton more. This is first time I see this kind of kind of division. Is this something from customer support? If somebody knew what's that let me know.
This is Azure DevOps work categories
If community is part of the process we don't need this.