A feature improvement tracker to accompany the bug tracker, so reports that could lead to improvement but are not considered bugs aren't lost.
Often when reporting a bug, it turns out it's not considered a bug because the issue has always been present. This means it's not a bug, and it's not a feature request (because the feature's there, but requires improvements).
When this happens, there's nowhere to report it, and possibly a suggestion that could lead to improvement is lost and forgotten.
I think it would be a good idea to create feature improvement tracker where people could report problems they're encountering due to the current design. This would reduce the amount of work the triage team have, and would also offer some good projects to new Blender coders (because the bulk of the work has already been done).
2 Comments
I support the idea, but i don't think it will go very far until the team decides that a significant design flaw can pragmatically be defined as a bug.
Easy example: Mark Sharp and Clear Sharp do different things, yet have identical tool tips. I suspect "Not a bug, because this was overlooked in QA and approved as it is. Please use RCS to request a new feature."
Or the weird situation with "Make Collection" vs "Create Collection"... etc etc.
I don't think they need to decide a significant design flaw is a bug. I just think they need to have a place for reported design flaws to live, so that developers who want to work on improving existing features have a list to work from 👍