Red Hat Bugzilla – Bug 826624
RFE: Automatically tag content specifications based on Product / Version
Last modified: 2018-04-20 17:29:07 EDT
Description of problem:
To further facilitate accurate searching and retrieval of content specifications it would be useful if the content specification was automatically tagged based on the PRODUCT and VERSION when it is uploaded to skynet. If for some reason the PRODUCT and VERSION changes then the tags would of course need to be updated.
Of course the onus here is also on us to set the product and version accurately to make this information useful...
You can actually accomplish this by setting the topic-wide metadata correctly in your content spec before uploading. Does this render this bug obsolete?
(In reply to Misty Stanley-Jones from comment #2)
> You can actually accomplish this by setting the topic-wide metadata
> correctly in your content spec before uploading. Does this render this bug
It's been 12 months but I believe the intent was for the metadata for these tags to be derived automatically from the product and version settings towards the top of the spec file rather than having to repeat the values again in the tag line. Note that this would (potentially) also require automatic creation of said tags if they did not already exist.
Hmm, I'm not sure this is the best way to go about it, especially creating the tags when they don't exist. I should also mention that while the UI doesn't support searching those fields atm, it will in the future (similar to the CLI searching).
As for the tags in the global section of the Content Spec they aren't meant to be a direct correlation to the Content Spec tags and instead are there to provide an easy way to bulk tag topics in the Content Spec (I ran into this pitfall myself recently). So perhaps what we need is a new MetaData field (or some other way) to assign Tags for the Content Spec, that doesn't influence the topics?