There's no way to do this built in. The reason is that it's not scalable.
Imagine I'm one of your users, with "access" to project XYZ only. Your system has 5,000 projects, with different fields for different types of project, and maybe 100 custom fields. Now think through the overhead of checking if every field is used by XYZ. Not so bad itself, but that's still 100 checks. Now imagine I have access to 200 projects - that's 200,000 checks to do.
The current solution is more simple - look at the global list, let people select them, then realise the fields are empty. If you have good admins, you won't have huge numbers of fields, or fields with confusing or contradictory names, which means your people probably won't have any problem finding the ones they actually need.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.