# Tag behavior not always consistent **URL:** \ **Category:** Bug\ **Created:** [October 7, 2021, 3:11pm UTC](https://meta.discourse.org/t/tag-behavior-not-always-consistent/205457 "2021-10-07T15:11:21Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![cristy](https://avatars.discourse-cdn.com/v4/letter/c/ccd318/32.png) [@cristy](https://meta.discourse.org/u/cristy)\ **Post date:** [October 7, 2021, 3:11pm UTC](https://meta.discourse.org/t/tag-behavior-not-always-consistent/205457/1 "2021-10-07T15:11:21Z")
Our desired behavior is for any new topic to compel the user to click on one group tag, Business\_Segment, and then select which business segment they belong too. What we instead see is that for any new topic request, an ‘optional tag’ pulldown is offered where some users, once clicked, can see the Business\_Segment group, but other do not. And although all categories are configured the same, these same users might see the Business\_Segment tag group on some categories but not others. Note, as an administrator, I am always presented with the Business\_Segment tag for all categories even though for other non-administrative users it is sometimes presented and other times, not. Our min trust level is 0. For each category there are no restrictions on tags or group. Instead we set ‘Num Tags’ to 1 and ‘Tag group’ to ‘Business Segment’. Business Segment is a tag group with associated tags of segment1, segment2, … We’re running 2.8.0.beta6. Running on a stable release might be recommended, but we just recently deployed Discourse on an on-prem VM and this is where we landed. It appears it is not recommended to revert to a stable release. 1. Can we compel the user to select the business segment tag instead of presenting it as optional? 2. How can we get consistent tag behavior-- where every new topic is presented with the Business\_Segment tag and upon clicking the choice of segment1, segment2, etc. Thanks, --- _[View the full topic](https://meta.discourse.org/t/tag-behavior-not-always-consistent/205457)._