# Documentation tag and Get Help

**URL:** <https://forum.ansible.com/t/documentation-tag-and-get-help/1889>\
**Category:** Forum Guide & Feedback\
**Tags:** documentation\
**Created:** [October 23, 2023, 10:09pm UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889 "2023-10-23T22:09:23Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [October 23, 2023, 10:09pm UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889/1 "2023-10-23T22:09:23Z")

</div>

Would it be possible to prevent the #documentation tag from being used in the #Get Help section? People are tagging random help posts with #documentation when it should really only be used in #Project Discussions.

---

<div class="post-metadata">

**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\
**Post date:** [October 24, 2023, 3:34am UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889/2 "2023-10-24T03:34:46Z")

</div>

Hi @gotmax23. yes, technically it’s possible to limit it to the #Project Discussions, but in my opinion, the #documentation tag is in a grey area in certain situations, particularly around (help) issues where the documentation is lacking. wrong or hard to find, and having that tagged is useful, not only for the day to day who are following the tag and willing to help on that front but for follow-up analysis.

For example, the following posts seem to be making good use of the tag:

> [@Ansible-builder using private registry](http://forum.ansible.com/t/ansible-builder-using-private-registry/1882):
>
> I’m working through migrating our current python virtual environments over to execution environments. I haven’t been able to figure out how to pull python modules or container images from our private repository/registry, which needs a username/password to auth to. I have a requirement where all python modules and container images need to be pulled from our repository/registry. I didn’t see anything in the Execution Environment Setup Reference documentation for this. Any help or direction on w…

> [@Where to get AWX openapi spec file](http://forum.ansible.com/t/where-to-get-awx-openapi-spec-file/1200):
>
> Hi community, on my current project we want to call AWX REST Api, however the requirement is to use Azure API Management as proxy. Is there somewhere AWX openapi yaml file that I can download and import into Azure APIM? Currently, AWX REST Api has over 100 resources, I don’t want to write yaml if I don’t have to. Why is it so difficult to find AWX openapi spec to download? Thanks

> [@Molecule - Setup, documentation, and testing](http://forum.ansible.com/t/molecule-setup-documentation-and-testing/626):
>
> I’m hoping to be able to get some assistance with configuring Molecule 6, as the documentation page is either lacking or I’m not understanding it. After creating the molecule/default directory and the files inside using the molecule init scenario --driver-name docker command, running molecule create will supposedly create the container, but it is no listed with docker ps and molecule login returns a FileNotFoundError for instance\_config.yml. Looking at the create.yml file there are some commen…

---

<div class="post-metadata">

**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\
**Post date:** [October 24, 2023, 8:33am UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889/3 "2023-10-24T08:33:32Z")

</div>

I think it’s to tag things with #documentation in Help too, especially where we’ve found a user’s problem and _then_ decided the issue is really with the docs. @acozine asked me some time ago to consider how we will use the forum to improve our docs, and I think this is part of that process (i.e. a search on `status:solved` and #documentation)

One thing we don’t have yet (because the forum is new) is a set of organically home-grown Trust Level 3 users. TL3 people have edit tags on other people’s posts, so once that is more common I expect to encourage those people to help us with the gardening 🙂

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [October 24, 2023, 2:43pm UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889/4 "2023-10-24T14:43:14Z")

</div>

What I’ve been doing is just filtering on projects with the docs tag when I want to see stuff that isn’t in the help section. But I also agree that having help tagged with docs is valid, so long as it is pointing out a docs problem. We should be reviewing those tags to be sure they aren’t getting mislabeled for example.

---

<div class="post-metadata">

**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\
**Post date:** [October 24, 2023, 3:42pm UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889/5 "2023-10-24T15:42:26Z")

</div>

For the record, I have been tagging posts that mention docs issues (like the ones I quoted above) with the #documentation tag, so I might be one (although probably not the only 😃 ) to blame if that wasn’t intended.

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [October 24, 2023, 4:02pm UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889/6 "2023-10-24T16:02:33Z")

</div>

I don’t know if something changed recently, but I’m no longer able to add the `documentation` tag to our meeting logs… anyone know what changed since last week?

---

<div class="post-metadata">

**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\
**Post date:** [October 24, 2023, 4:05pm UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889/7 "2023-10-24T16:05:13Z")

</div>

Mmm, I was having that issue here in #Project Discussions an hour ago, and had to go add the tag groups to the category. So, it’s probably my fault, let me go check

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [October 24, 2023, 4:05pm UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889/8 "2023-10-24T16:05:36Z")

</div>

They are also not showing in the same place anymore. This is where they used to be - [Workflows & Logs - Ansible](http://forum.ansible.com/c/workflow/15)

And today’s is showing up at [MeetingBot Logs - Ansible](http://forum.ansible.com/c/workflow/meetbot/16)

---

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [October 24, 2023, 4:05pm UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889/9 "2023-10-24T16:05:36Z")

</div>

Okay, so it seems we have a legitimate reason to tag things with #documentation in #Get Help. Thanks for the feedback. I guess we’d need something like [Allow subscribing to an intersection of category + project](http://forum.ansible.com/t/allow-subscribing-to-an-intersection-of-category-project/1157) implemented instead of just limiting the #documentation tag.

---

<div class="post-metadata">

**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\
**Post date:** [October 24, 2023, 4:07pm UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889/10 "2023-10-24T16:07:59Z")

</div>

OK, undid that silly change, mea culpa. Should work now.

> [@samccann](#):
>
> And today’s is showing up at [MeetingBot Logs - Ansible](http://forum.ansible.com/c/workflow/meetbot/16)

That was changed some time ago, I see the last month’s worth of Docs logs in #MeetingBot Logs

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [October 24, 2023, 4:15pm UTC](https://forum.ansible.com/t/documentation-tag-and-get-help/1889/11 "2023-10-24T16:15:57Z")

</div>

yeah, I can see them all there now and can add the documentation tag to the meeting logs again, thanks!
