# Problems with group names

**URL:** <https://hub.mender.io/t/problems-with-group-names/6385>\
**Category:** General Discussions\
**Tags:** mender-client\
**Created:** [November 27, 2023, 4:55pm UTC](https://hub.mender.io/t/problems-with-group-names/6385 "2023-11-27T16:55:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mnavarro](https://avatars.discourse-cdn.com/v4/letter/m/a9adbd/32.png) [@mnavarro](https://hub.mender.io/u/mnavarro)\
**Post date:** [November 27, 2023, 4:55pm UTC](https://hub.mender.io/t/problems-with-group-names/6385/1 "2023-11-27T16:55:08Z")

</div>

When I go to inventory a device and I want to change it to a group, instead of the group name I see the numbers.

Before I saw/knew which group I was adding it to because the name appeared, but now I don’t.

HELP pls

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [November 27, 2023, 8:31pm UTC](https://hub.mender.io/t/problems-with-group-names/6385/2 "2023-11-27T20:31:33Z")

</div>

Hi @mnavarro,

Thanks for the report, this is a known issue which came with the new deployment of Hosted Mender. We apologize for the inconvenience this regression have caused.

The issue has already been reported and will be worked on in a timely manner. Until it is resolved, the workaround is to add the device to a group is to reenter the name of the existing group and press “Create group” (although it exists already). This will add the new device to the group.

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [November 28, 2023, 11:19am UTC](https://hub.mender.io/t/problems-with-group-names/6385/3 "2023-11-28T11:19:40Z")

</div>

Hi @mnavarro,

The fix was just deployed. I’ll mark this as resolved for now, feel free to comment below if the problem persists.

Greetz,  
Josef
