Custom Tag predicates cannot be permanently configured to only pull specific namespaces

[#1]

Request for Feature Enhancement (RFE) Summary:	Custom Tag predicates cannot be permanently configured to only pull specific namespaces
Use-case:	We want to have multiple tag fields not just one
Current/Experienced Behavior:	AEM has an out-of-the-box tag field. There are certain instances wherein stakeholders would like custom tag fields configured for certain tag groups. E.g. A tag field for “Content Type”, “Target Country(ies), “Campaign”. In the schema editor, there is no out-of-the-box way to limit what namespace is going to be displayed on a certain tag predicate. With that, even if there are multiple tag fields created, all of them will display the same set of tags or tag groups
Improved/Expected Behavior:	Have the ability to point tags fields to a specific namespace
Environment Details (AEM version/service pack, any other specifics if applicable):	AEMAaCS
Customer-name/Organization name:
Screenshot (if applicable):
Code package (if applicable):

[#2]

This would be a great addition

[#3]

Hi @mikeetiuPH 

Thanks for proposing the idea. This request has been raised to the product team via the internal request CQ-4326979. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

[#4]

Thanks, @mikeetiuPH, This issue has been added to the product backlog.