# \[Tagging\] Updates FYI

**URL:** <https://community.frame.work/t/tagging-updates-fyi/27206>\
**Category:** Linux\
**Tags:** linux-announcements\
**Created:** [February 13, 2023, 6:50pm UTC](https://community.frame.work/t/tagging-updates-fyi/27206 "2023-02-13T18:50:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\
**Post date:** [February 13, 2023, 6:50pm UTC](https://community.frame.work/t/tagging-updates-fyi/27206/1 "2023-02-13T18:50:39Z")

</div>

Just so everyone knows, we are bringing back [Tagging] outside of merely just marking something as solved. This was discussed by my team and it has been determined not doing this makes tracking posts a lot more difficult. So this is what is happening.

[SOLVED] This will mean the OP of the thread has resolved the issue either on their own or with help.

[TRACKING] This is an active issue that we’re gathering data on and is active. Mods, do not remove these tags please.

[IN-TICKET] These threads are tagged as duplication from an active ticket with support.

[RESPONDED] Issue requiring our eyes, so we’re aware of it and appreciate the feedback.

---

<div class="post-metadata">

**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\
**Post date:** [February 13, 2023, 6:50pm UTC](https://community.frame.work/t/tagging-updates-fyi/27206/2 "2023-02-13T18:50:51Z")

</div>


