this is a list of currently 163 requests in sequential order.
I will not read through it, of course.
Without a helpful structure, it is not information, but only noise.
So, my proposal:
reorganize it in a requirement-management fashioned way. Make it hierarchical. Apply a useful structure, so that the user can do a binary search instead of full read.
A useful structure would be the structure of TC's technical elements.
And, further: include status information. Has a request been discussed, is it accepted, rejected for what reason,..?
Provide filter & search functions on status and content.
Regards,
Manfred
