tagging ideas with "problems solved"

I have experience with programming problems that have had multiple solutions. Althought don't forget, solutions aren't always software. Imagine for example that launching Photoshop causes a loud buzzing sound on some computers. One solution is to do more thorough testing of sofware updates on a wider range of computers, another might be discontinuing a feature in Photoshop and implementing it into Illustrator, yet another might be asking users to wear noise cancelling headphones. You are limited only by your imagination! This is more obviously true with problems that are more generic, such as "UI is too busy/complicated" which has virtually infinite solutions. My suggestion is that is users were free to add their own tags, it would be easier to identify patterns in terms of the relative abundance of various problems. For solutions that leverage AI, providing tags is a way of giving it more structure and "context engineering" so that patterns can be more quickly and reliably identified.

This is true, and irrelevant to my point.

"a single problem has many possible solutions,"

=========

Not usually. Most apps work on the Boolean principle of On/Off or True/False statements. 

I program web apps, so I know this to be true (pun intended). 

Forum moderators already merge related posts into a continuous topic for easier consumption by the engineering team's internal data tracking software. This can be seen regularly in Photoshop and Lightroom forums like this one.

https://community.adobe.com/t5/lightroom-classic-ideas/p-bring-back-the-ability-of-enhance-to-run-in-the-background-lrc/idi-p/15374596

Bugs & Ideas are then evaluated & prioritized by team management based on various factors. Urgent bug fixes usually get sent out in incremental product updates. Complex bugs & new features are often addressed in major upgrade cycles. 

Unless I'm missing something, I'm not sure how AI fits into that. 

Can you give us some actual examples?

People supporting the idea want to have that idea fulfilled. They can and will leave a comment on how that will help them. 

Yes it is assumed that there is a problem. But a single problem has many possible solutions, in other words problems and ideas have a "one-to-many relationship". What I'm suggesting is a way to track how many people are having the same problem, independent of how many people support a specific idea.

I think that's already assumed. Nobody posts feature requests in IDEAS unless they've identified some kind of problem (usability, access, convenience, etc...) that needs a solution, right?