Same for Workstreams. I get a similar message to this for Boards - seems like a bad experience for the end-user to have an option available to them that isn't set up. 

@Jashley13   New Commenting Beta experience also on full 23.2 enhancements: 23.2 Release overview

The same is true when commenting during the approval of a task, issue, or project - you can't tag anyone so no one knows a comment has been made. AND no one is notified of either the approval or the rejection, which causes things to fall through cracks. We're looking at creating a report to track ce...

@Kiesner10  Users themselves can bring a task back to their work list after closing it just by clicking Not done yet, where the Done button was before they clicked it. It gets trickier if someone else is saying the task isn't complete. For example if there are multiple people assigned to the task, w...

@jon_chen  Maybe this idea and Monique's linked above can be combined?

I see this becoming an issue at my new company as our IT also bars us from being able to install apps.

This would be great! I've avoided defaulted values in custom fields for this very reason.

Good call out @Doug_Den_Hoed__AtAppStore having both a native and custom field with the same name makes for a reporting nightmare - and reporting includes creating any filter/view/grouping on any list, not just strictly in the reporting area. You don't know which field to pull into your report when ...

Another feature I'd like to see related to this is if you create a custom field with exact same name as a native field, you'd receive at the very least a warning, preferably not be allowed to create a custom field with that same name.

This would be great for Column Rules, I'd also like to be able to drag/reorder Groupings and Prompts. To re-order those it's also currently a case of delete/re-add