So, I believe we all agree that version-specific tags are valuable, right? The question now is if the umbrella / parent (like ms-project) tags are also useful or not. I can't think from the top of my head about a practical question to be asked on ms-project that won't be version specific (at least based on the latest questions asked)... It'd be useful from a personal filtering perspective (someone wants to follow ms-project questions regardless of versions) but besides this... any other value?

Version specifics are useful when they make sense to be used at. If a person uses ms-project-2017 just because that's the version (s)he is using, then there will be space to delete that tag and just use ms-project

In stack angular has plenty of specific tags: angular2, ng2-whatever, angular ... in that case if one doesn't edit tag, the question won't even get the needed attention

So, it has two sides: users won't be able to filter through parent tags and if they miss upon one specific version, then the question won't have enough attention on its own

The advantage in this community is people don't post that often, so it wouldn't probably suffer from that initially. But as long as the community grows, that problem will appear and then it will require effort to implement the parent tags

@TiagoCardoso I don't actively use Project, but I can't imagine that the entire workflow is different version to version. Process questions or "how do I do X in Project?" type questions are likely to be the same (or at least similar) in any version. With that said, I don't mind removing the umbrella tag, but the easiest thing to do is just to put something in the tag guidance that says something like "use this tag only for MS Project questions that aren't version-specific."

Sharing my personal experience with other communities, I find the umbrella tag quite useful, for a variety of reasons:

- It helps people be seen as experts in a specific field (let's admit it, some people seek that)

- Useful for searching for content related with that software/area, as some of the problems are transversal

*for searching content

- Makes the community more user friendly, as some newbies may use one tag or another and still get their answers solved (following along the 1st point)

And more... Oh, I didn't mention but I share most of the thoughts mentioned by @tiagoperes. Also, he pointed out real ways to deal with the problem in hand, as this situation occurs in all the communities. But at the end, it is up to each community to specify their standards/procedures. I am willing to help in the process of standardization

Agree on the value added by having both tags (umbrella + version-specific). Just concerned about messing with the main feed (which may not become a problem once most of the questions are tagged).

tried using the edit and edit tags to see if there was any diff... no luck

so, just did a query search and will update the remaining items

will mess up with the news feed... once

... and Gonçalo as well (thanks!!)

ok - 57 updates done... I guess most questions are now tagged

guys, now we have a wave of "pm-software" tagging... do we need this retagging queued up on the edit approval queue? Shouldn't we wait a bit to do them when there's enough rep to no longer need edit review? Any thoughts?

besides, shouldn't we simply assume that a question tagged ms-project is about pm-software?