-
Notifications
You must be signed in to change notification settings - Fork 74
How will we get to user issues
YingXue edited this page Dec 2, 2022
·
3 revisions
- Template
- Issues that we asked follow up questions to the reporter, will be auto closed if there is no response after X days.
- Issues that have been tagged in a PR/Release, will be auto closed once Release is out.
- Severity
- Should we introduce severity to the issues to help prioritize them?
- Should they be visible to the reporters?
- Issue categorization
- Bugs vs Feature requests.
- For areas that we don't actively develop, how do we keep ourselves honest to the users?
For example, I am adding 'pnp' tags to a lot of issues which has been open for a long time to prevent myself from checking on them repeatly. Especially for feature request in this area, those issues are being pushed to the bottom and it's possible that we will never get to them.
Another example is about AAD support. What we enbaled is so limited, and users expectation is our AAD story should be on par with Azure Storage Explorer for example, where they can pick the tenant and do more sophosicated operations. With features that we don't have a clear spec, how do we respond to those issues.
- ICM rotation Refer from last meeting notes.