1. Resources Label was chosen because it isn't a "display name" and this was causing the field to be used in places where it was ambiguous as to which DS it referred to. "Resource's Tree Label" was too much for UX to stomach for a field name.
2. It's Markdown.
3. We've since added the Uiv3 wizard functionality back. Would love your feedback on it.
4. The collection method changes which collection options are shown, hence the order.
5. Not sure I understand the criticism here, but lots of the ordering was dictated by what is common vs changing among different types/options.
6. I don't really get people asking for this. It hasn't been on our radar. I've had other improvements considered for Test AD and Test Script (showing script output as well as parsed output) but these have not been prioritized.
7. I imagine this is a pretty global pattern but haven't heard any complaints. It would be nice to have it scroll to where the issues are.