I think "Tags" in the Property List context is incorrect, since other data about the Project (like the Workboard its on) is also provided.

But maybe @epriestley did want this field changed also?

I see. It's also still "Projects" in Maniphest - I assumed the intention was to rename it everywhere where "projects" carries similarities to "tags" in a broad sense, since a common misconception about our users is for example that repositories or tasks "belong" to one project alone. I already explained that this is not the case to most of them several times and also wrote it in our internal documentation, but it still comes up, especially for people new to Phabricator. Thus I assumed that this is also a common misunderstanding in other groups and the renaming effort is targetted at this exact problem.

Understood, I just don't know if it was intentionally not converted (@epriestley made the changes). It's just one line in the code and it'll update on all the Property Lists. Do you feel Tags is better everywhere over Projects. That is, are your users less confused about the product?

I think it's probably better, but renaming it causes this in Diffusion:

I'll probably try to figure out something to do about that, then rename it if I come up with something reasonable.

I think I suggested "Project Tags" at one point.

In T10326#158479, @chad wrote:

I think I suggested "Project Tags" at one point.

That's also what it's called in Maniphest, when adding them: Actions → Change Project Tags

To prevent confusion with Git/Hg/Svn tags: What about "Label"?

To add to this, viewing a Task shows "Projects" whereas editing it shows "Tags". This caused confusion to one of my users, who couldn't find where to update the Projects while editing a task.