Bit strange, this thread reads as a what you usually see in beta feedback processes.
If you want to approach this from angle of priorisatisation and categorisation, keep in mind that most of it will always be highly subjective. But that is ok, individuals buy stuff, so is just a case of weighing how much volume assigns priority to an issue.
Still, list strikes me as big caught between two sides. One side of bugs, annoyances, complications, missing "obvious" bits. Other side being the angle of bigger things, the level of complexity (as opposed to complications), feature elements and content.
First part, there is maybe room for. Probably is room for, now that release is out and support cycle is active, until it is time for picking up on the second part (for addons, expansion packs, DLC, gold packs, etc). So, second part now simply no resources for.
Maybe a way to streamline such a list for first part / side / angle is (with polls if need be) along principle of
moscow (or muscow, depending on where you went to school).
M - MUST (have this)
S - SHOULD (have this if at all possible)
C - COULD (have this if it does not affect anything else)
W - WON'T (have this time but WOULD like in the future)
Obviously this is written from customer perspectives. Not publisher or developer. But the last two want to sell stuff, so they have to be smart. In community processes, this is not an easy task, but with the help of categorisation by type (as opposed to element) you can weigh how much support an item gets.
M and S "types" are really what such list can focus on. S can feature a change, but keep in mind the design phase is over, there won't be much big commitment. Product is finished, support cycle has begun. C and W are set in stone by developers (sometimes for developers by owners and sometimes even publishers), only of interest for expansion pack or DLC.
Everything else is bugs or unintended use patterns, 2K Games forums has some of that I see, but is a mess so never hurts to apply same approach to as part of list.