Using Project Tags at scale with removed group limits and predictable permissions

Project Tags are a lightweight and easy way to organise your Projects into bespoke criteria. They also have great synergy with Project Collections to help you visualise your grouping criteria (such as teams or services), focus work, and generate reports.

However, there has traditionally been a couple of points of friction when it comes to using tags at scale:

• You could only create 1000 tags per group, which meant that you might hit your limit quickly (even with good tag management).

• Different permissions were required to create a tag within a group, and assign a tag to a Project, so even if you had an org role that would allow you to work with tags on a project, you might not have the group permission that allowed you to create the tag.

Ultimately, users want the ability to group their Projects by any criteria without any limits, and to not work inefficiently because they're blocked by permission issues. So we're pleased to announce that we have removed the group tag limit, and we're making tag permissions more predictable in behaviour.

The org permission to assign and remove a tag to a project is now sufficient for all tags and will be applied to group admin, org admin, and collaborator roles whilst the permissions for custom roles will remain as they were before this work was delivered. The two differences to your experience will be:

• When you create a custom role, you do not require separate group permission to work with tags, which also helps improve security as you don't need to provide users with group permissions to enable org level functionality.

• The concept of creating and deleting a tag no longer exists. If a tag isn't assigned to a Project, it will not exist.

All of the Project Tag APIs will continue to work as they currently do today.