# Recent changes about default labeling

**URL:** <https://forum.ansible.com/t/recent-changes-about-default-labeling/29699>\
**Category:** Ansible Developer\
**Created:** [February 18, 2019, 4:09pm UTC](https://forum.ansible.com/t/recent-changes-about-default-labeling/29699 "2019-02-18T16:09:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mperina](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@mperina](https://forum.ansible.com/u/mperina)\
**Post date:** [February 18, 2019, 4:09pm UTC](https://forum.ansible.com/t/recent-changes-about-default-labeling/29699/1 "2019-02-18T16:09:09Z")

</div>

Hi,

I’m one of oVirt modules maintainers and and we were using “ovirt” label to filter issues related to oVirt Ansible modules [1].

Today I’ve found out that “ovirt” label doesn’t exist anymore and instead all issues around various virtualization related modules are labeled with “virt” label.But this is a huge issue for both oVirt developers and QEs, because we don’t have any way how to easily filter issues related to oVirt modules.

So can this change be reverted and can all issues related to ovirt modules [1] be again labeled with “ovirt” label?

Thanks a lot

Martin

[1] [https://github.com/ansible/ansible/tree/devel/lib/ansible/modules/cloud/ovirt](https://github.com/ansible/ansible/tree/devel/lib/ansible/modules/cloud/ovirt)

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [February 18, 2019, 5:19pm UTC](https://forum.ansible.com/t/recent-changes-about-default-labeling/29699/2 "2019-02-18T17:19:59Z")

</div>

Hi,  
Looks like this got changed to [GitHub · Where software is built](https://github.com/ansible/ansible/labels/virt) which should apply to everything once the bot has caught up.

---

<div class="post-metadata">

**Author:** ![mperina](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@mperina](https://forum.ansible.com/u/mperina)\
**Post date:** [February 18, 2019, 5:49pm UTC](https://forum.ansible.com/t/recent-changes-about-default-labeling/29699/3 "2019-02-18T17:49:03Z")

</div>

> Hi,  
> Looks like this got changed to [https://github.com/ansible/ansible/labels/virt](https://github.com/ansible/ansible/labels/virt) which should apply to everything once the bot has caught up.

Yes, but it also labels modules from different projects like proxmox or libvirt, so there is no easy way how to easily filter open issues for oVirt modules only.  
So is there a way how to automatically label oVirt modules with “ovirt” label as before?

---

<div class="post-metadata">

**Author:** ![mperina](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@mperina](https://forum.ansible.com/u/mperina)\
**Post date:** [February 18, 2019, 6:23pm UTC](https://forum.ansible.com/t/recent-changes-about-default-labeling/29699/4 "2019-02-18T18:23:39Z")

</div>

> > Hi,  
> > Looks like this got changed to [https://github.com/ansible/ansible/labels/virt](https://github.com/ansible/ansible/labels/virt) which should apply to everything once the bot has caught up.
> 
> Yes, but it also labels modules from different projects like proxmox or libvirt, so there is no easy way how to easily filter open issues for oVirt modules only.  
> So is there a way how to automatically label oVirt modules with “ovirt” label as before?

Ahh, I’ve found out where labeling is configured and created [https://github.com/ansible/ansible/pull/52510](https://github.com/ansible/ansible/pull/52510) to restore ovirt label again