Hi Steve Stern (@sterndata),
Thanks for the link.
Very helpful.
Is it possible that when the user receives a ‘notice of delay’ that the notice also could include the reason why?
This could be automated, or the moderators could tick a checkbox as to why and the corresponding text and link appended to the delay message.
This would be a significant help to the user, so they get the earliest possible notification after misuse, and reminders.
It would also be helpful to have the reminder remain either in the users page, or the respective topic so they can avoid repeating the same thing.
It would also cut down recurrence or the likelihood of recurrence, which would also save time for moderators.
A thought on the “no replies” information in the link;
(note- I had not added comments to try to get to the top of a general list. I had added comments thinking that the plugin authors may have added the topic to something like a “following” list, and that this would show up as a topic with some recent activity – rather than long stagnant. However, I now understand that this assumption is incorrect, and read in the link that removing the additional comment actually helps to keep the topic closer to the plugin authors attention.)
The method used to search for topics, is to look for topics with “no replies”.
But more specifically the particular search is for “no replies from [The volunteers who try to answer questions]”. There is no way to distinguish a reply based on the status or category or group that the replier belongs to.
If the database could record whether the topic had been replied to by the correct responder, then it would not matter who else, or how many times further comments are added, it will still show up as unreplied to by themself or their group.
But in any case, if they were to search for “unresolved” topics, then they could see to topics that are still outstanding.
But those are just some thoughts on what might be a way to improve the system.
Thanks for your assistance.
I will try to avoid doing this again.
The problem is I have done this before and later forgot again.
And so I might end up doing it again.
Both these events happened when many plugins were being reported as not compatibile (first with php 6, then 7, and now woocommerce), which meant many new topics, and a sense of urgency to get systems into a robust state.
I would like to avoid a repeat, and this is why a reminder via a “reason why some comment has been queued” in the delay message, would be quite a help.
Please accept my apologies?