# Opening issues against all collections in Ansible for core-2.19 template testing

**URL:** <https://forum.ansible.com/t/opening-issues-against-all-collections-in-ansible-for-core-2-19-template-testing/41678>\
**Category:** Collection Development\
**Tags:** templating, community-wg\
**Created:** [April 11, 2025, 1:44pm UTC](https://forum.ansible.com/t/opening-issues-against-all-collections-in-ansible-for-core-2-19-template-testing/41678 "2025-04-11T13:44:07Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [April 13, 2025, 12:38pm UTC](https://forum.ansible.com/t/opening-issues-against-all-collections-in-ansible-for-core-2-19-template-testing/41678/5 "2025-04-13T12:38:40Z")

</div>

Some practical advice might be helpful and sounds like a good idea to me. But I wonder if this wouldn’t make the issue text very long. And it would be also hard to add more practical advice in case it would be useful or needed.

How about having the advice from @felixfontein somewhere else and just add a link to the issue? Maybe on the forum. We could re-use [Data tagging playground](https://forum.ansible.com/t/39909) for this or [Data Tagging preview and testing](https://forum.ansible.com/t/40759) or create a new thread like `Making a collection compatible with data tagging` or something.

Then we would have a central place to add more advice when needed. And this would also mean that we can answer general questions in one place once instead of repeatedly in several issues.

---

_[View the full topic](https://forum.ansible.com/t/opening-issues-against-all-collections-in-ansible-for-core-2-19-template-testing/41678)._