# Adding a more visual "solved" status indicator?

**URL:** <https://forum.ansible.com/t/adding-a-more-visual-solved-status-indicator/1795>\
**Category:** Forum Guide & Feedback\
**Created:** [October 19, 2023, 8:31am UTC](https://forum.ansible.com/t/adding-a-more-visual-solved-status-indicator/1795 "2023-10-19T08:31:52Z")\
**Posts on this page:** 7\
**Page:** 1

<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 19, 2023, 8:31am UTC](https://forum.ansible.com/t/adding-a-more-visual-solved-status-indicator/1795/1 "2023-10-19T08:31:53Z")

</div>

@samccann has pointed me at [this component](https://meta.discourse.org/t/solved-topic-badge/281981) which can add a more vibrant indicator of solved/unsolved topics in #Get Help. While advanced users know how to use the search for finding unsolved topics, this helps newer users.

Here’s how it looks on our forum:

 ![2023-10-19-092757_843x420_scrot](https://us1.discourse-cdn.com/ansible/original/2X/1/1d28bb7ddddb7a61b42af7cd9635959934465fa6.png)

I’ve played around with it, and I think “styled” is definitely better than “inline”, but I’m unsure if we want it “before-title” or “after-title” (the above shot is after)

Here’s the same frontpage region in each style:

 ![2023-10-19-092511_1097x514_scrot](https://us1.discourse-cdn.com/ansible/original/2X/9/94299f78db5ad2425331fa2b9cfbd5167429bfab.png)  
 ![2023-10-19-092419_1105x562_scrot](https://us1.discourse-cdn.com/ansible/original/2X/8/8c911c4f546fb4cb20ac309121693d8b32bc0a0d.png)

I _think_ I prefer the “before-title” as it keeps it all in a neat column, but what are your thoughts? Let’s have a poll!

_Poll ([view on site](https://forum.ansible.com/t/adding-a-more-visual-solved-status-indicator/1795/1))_

I’ll count the Yes votes together for decided if we use it at all, of course.

---

<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 19, 2023, 8:33am UTC](https://forum.ansible.com/t/adding-a-more-visual-solved-status-indicator/1795/2 "2023-10-19T08:33:16Z")

</div>

I’ll add that for people who are trying to reduce visual noise, I won’t add this to the “Simple” theme, so there’s a way to turn it off

---

<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, 4:03am UTC](https://forum.ansible.com/t/adding-a-more-visual-solved-status-indicator/1795/3 "2023-10-24T04:03:06Z")

</div>

I’m voting no, but not because it’s unhelpful, but because I find it too loaded and distracting from the titles as proposed. In my particular case I think the noise outweighs the benefit.

That said, I do think it’s useful, so looking at the plugin settings, maybe if we disable the “unsolved” indicator, it would make it less intrusive, considering most of the “latest topics” will be in that situation and the ones we care to “highlight” would be the solved ones.

I’m not sure the settings allow to actually “disable” the unsolved indicator, but looks like it can be done with a workaround if we wanted (maybe no indicator, no label, transparent background will do the trick?).

---

<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:30am UTC](https://forum.ansible.com/t/adding-a-more-visual-solved-status-indicator/1795/4 "2023-10-24T08:30:05Z")

</div>

> [@Leo](#):
>
> I’m not sure the settings allow to actually “disable” the unsolved indicator, but looks like it can be done with a workaround if we wanted (maybe no indicator, no label, transparent background will do the trick?).

It works but it causes other odd effects (like the 🔵 notification moving to the right). Looks weird to me.

> [@Leo](#):
>
> I’m voting no, but not because it’s unhelpful, but because I find it too loaded and distracting from the titles as proposed. In my particular case I think the noise outweighs the benefit.

As I said, we will leave it disabled on the Simple theme, for those who prefer a less noisy UI, does that help you?

---

<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, 1:55pm UTC](https://forum.ansible.com/t/adding-a-more-visual-solved-status-indicator/1795/5 "2023-10-24T13:55:11Z")

</div>

> [@gwmngilfen](#):
>
> It works but it causes other odd effects (like the 🔵 notification moving to the right). Looks weird to me.

That’s too bad.

> [@gwmngilfen](#):
>
> As I said, we will leave it disabled on the Simple theme, for those who prefer a less noisy UI, does that help you?

I’m trying it now. Not sure what the differences are between the default (aka simple) and Material, but even if it solves it for me personally, I still think that if we default to showing a bunch of topics “unsolved” is noisy for new users and not a good first impression.

---

<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:** [August 27, 2024, 4:52pm UTC](https://forum.ansible.com/t/adding-a-more-visual-solved-status-indicator/1795/6 "2024-08-27T16:52:43Z")

</div>

Should this poll be closed now?

---

<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:** [August 28, 2024, 8:00am UTC](https://forum.ansible.com/t/adding-a-more-visual-solved-status-indicator/1795/7 "2024-08-28T08:00:36Z")

</div>

We can yes, although I’m still thinking that @leo raised some good points…
