View tag changes

[adrelanos]

Could you please add the ability (for moderators) to view tag changes?

Currently if any tag is changed anywhere there is no place to review these.

The closest similar thing is /admin/reports/post_edits but that does not show if any forum tags (/tags) where changed.

In case you wonder why this would be useful: I would like to use discourse as an issue tracker. It’s not ideal but sufficient for my use case. There’s been discussions on how to use discourse as a ticketing system and it seems possible in principle. Using it as a public issue tracker seems even simpler than a ticketing system. (Users require forum accounts to post. E-mail in is nice but not crucial.) In my case, only important thing to track is the status of the discussion and milestone (software version implementation goal). Using tags this is possible (tag status_closed) etc. But for example if a user or moderator by accident or trolling removes tag “milestone” then a “ticket” (actually forum discussion) could be lost from that view.

To learn about such topic tag change events, the ability to view tag changes would be super useful.

[itsbhanusharma (Bhanu Sharma)]

I don’t know if you’ve already checked this but there is a plugin made specifically to handle tickets

Tickets Plugin

Repo Summary This plugin adds a ticketing system to Discourse. It requires tagging to be enabled and works best alongside the Assign Plugin. It is based on @tobiaseigen’s original spec, and has been built in collaboration with @tobiaseigen and an awesome Ruby for Good team, for the benefit of both Namati and the Discourse community. Notes When you install the plugin, three new tag groups are added tickets_priority, tickets_reason and tickets_status. Add tags to these groups (at /tag_group…

[adrelanos]

I saw this. I will consider it. Actually, I am in process of reading all subjects on discourse for issue tracking / ticket system.

For the use case as simple as mine, I was wondering if it would be doable / more sensible without an external plugin.

I hope my “view tag changes” request is useful enough outside of ticketing. Also please consider trolling / spamming where user edits its own post to add tag to add some badword.

Reason is, I’ve seen plugins here come and go. For now it looks well up to date but I saw other plugin discussions where I was too late for the party. The plugin was deprecated for two years already. Then I would hope to not be “stranded”. Migrating away from such as tickets plugin to another issue tracker in two or five years from now would be require a ton of time.

[maiki]

@adrelanos

Also please consider trolling / spamming where user edits its own post to add tag to add some badword.

The “fix” is to remove those users from the site.

@adrelanos

Reason is, I’ve seen plugins here come and go. For now it looks well up to date but I saw other plugin discussions where I was too late for the party. The plugin was deprecated for two years already. Then I would hope to not be “stranded”. Migrating away from such as tickets plugin to another issue tracker in two or five years from now would be require a ton of time.

There is also marketplace, so you can have a plugin supported/created.

[rishabh]

Je suis venu ici pour chercher la même chose. Si nous utilisons Discourse comme un outil de suivi des problèmes (en utilisant des sujets), il serait agréable d’avoir une liste de tous les changements de tags dans les ‘x’ derniers jours pour une catégorie/tag spécifique afin d’avoir un aperçu périodique ou un instantané de l’état actuel.

Discourse Data Explorer devrait faciliter cela, et je ferai un rapport ici si je trouve/crée une requête SQL.

[sam (Sam Saffron)]

pas facile du tout…

la colonne modifications dans post_revisions stocke un objet ruby sérialisé, vous ne pouvez donc même pas utiliser les fonctions JSON de PG pour cela.

nous devrions vraiment porter cette colonne en JSON.

[adrelanos]

@maiki

@adrelanos

Veuillez également tenir compte du trolling / spam où l’utilisateur modifie son propre message pour ajouter une balise contenant un gros mot.

La « correction » est de supprimer ces utilisateurs du site.

Bien sûr, mais pour un projet FLOSS public avec inscription ouverte, au moment où le trolling par balises a été effectué, les dégâts sont déjà faits. Par conséquent, un moyen de visualiser les changements de balises et de facilement annuler le vandalisme serait utile.

@rishabh

Discourse Data Explorer devrait faciliter cela, et je signalerai ici si je trouve/crée une requête SQL.

Des nouvelles ?

[Anat_Srulovitch]

Salut, je suis également venu ici à la recherche d’un moyen d’afficher les modifications de balises pour un sujet spécifique.
Ce serait très utile à avoir.
Merci !