Should it remove all matching claims or only one?
Should qualifiers and references be considered?
If claim doesn’t exist, what should happen?
Is backward compatibility of current claimit behavior required?

Thanks for the clarification!
Yes, it will list only the users who upvoted that specific suggestion (via upvoted_users), not all users.
I’ll work on a small PoC

@Aklapper Thank you for the clarification! I’ll make sure not to ping randomly in the future. Really appreciate your time and feedback.

@Aklapper can you check ?

@Samwalton9-WMF Instead of excluding upvoted_users, we should expose a read-only admin field that lists usernames and emails. This avoids accidental overwrite while allowing admins to access the information without querying the DB

@Xqt am i change other related file also?

@Xqt Thank you i am working on T416673 this issue

@Aklapper Thanks for the clarification. I’ll start working on this task in the TWLight repository and will share progress or questions here.

Hi @Samwalton9-WMF , I’m interested in working on this task.
I’ve reviewed the updated description and the TWLight repository.
Could you please confirm if the task is still available and whether hiding the upvoter list in the admin UI is the preferred approach?
Thanks!

@Xqt can you give advice which issue to work on next , seems no good-first-issue open in pywikibot.

@Xqt Thank you for merging my patch and for the guidance! I will make sure to amend future patches instead of creating new ones. I will also add myself to the AUTHORS.rst file. I really appreciate your help and feedback.

@Xqt can you check is this patch solve or need to change where

@NAGAM_SURYA_NARAYANA read this https://www.mediawiki.org/wiki/New_Developers#Communication_tips

Hi @ori , I’m interested in working on this task.
I’m learning Lua and would like to try fixing the ustring.gsub replacement behavior.
Please let me know if that’s okay.