I understand that requesting features towards Stack Exchange Inc. works like this:
- you write a question-request here on MSE
- the community votes, and adds more thoughts, concerns, enhancements, ...
- someone, somewhen makes a decision. When the decision is "no, won't happen", then the story ends there. If not ... there is no clear feedback when/how that request will be picked up. Maybe someday, the new feature is just there, or it gets announced as experiment. But the user making the suggestion, and the community statement "we like this" ... has no idea when that is, and how many other features have a higher priority at any point.
The voting mechanism makes sense, to get an understanding of the priorities that the community sees.
But these days, when you do agile software development (and SE Inc. wants to be agile, see here for example), shouldn't there be some backlog kind infrastructure, too?
In other words: in 2019, there are tools like Trello, Jira Agile, Jira Portfolio, or Pivotal Tracker, and many others. I assume that SE Inc. is using such a tool to plan its activities.
Wouldn't it be great if the community related parts of their planning data would be publicly available to us?
According to SE Inc., they intend to listen to us. Being able to see how feature requests progress on their development planning would be a really great way to give the community feedback about ongoing work/activities.
Edit: I do not consider Allow public tracking of feature-requests via view into Stack Overflow's ticket tracker to be duplicate that matches the intent of my question: defect trackers focus on low level information, such as "who touches module X at which point in time". I can understand that a company isn't eager about disclosing such internals. I don't want a level of detail that enables posts like "Look, SE Inc. engineer X takes double the time compared to Y, when they on community requested feature, why is that?"
What I ask for is to create transparency on the project planning side of things. Including "effort estimates", and appropriate information about "capacity" on the other hand, and the ability to quickly answer questions such as:
- What is worked on right now?
- When should that thing be completed, according to the plan? ...