Changes between Initial Version and Version 1 of Ticket #7161, comment 5
- Timestamp:
- 07/28/2023 07:42:47 PM (20 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #7161, comment 5
initial v1 1 Most support ticket systems have a "reply and close" option. I think many plugin developers with a large volume of support tickets would be familiar with that. We deal with a lot of support tickets via Zendesk and control when they close on a per-ticket basis, and I don't think it's a significant burden. Honestly, giving plugin contributors the ability to close threads would be nice because they could close them before the 6 montmark if they want.1 Most support ticket systems have a "reply and close" option. I think many plugin developers with a large volume of support tickets would be familiar with that. We deal with a lot of support tickets via Zendesk and control when they close on a per-ticket basis, and I don't think it's a significant burden. Honestly, giving plugin contributors the ability to close threads would be nice because they could close them before the six-month mark if they want. 2 2 3 3 I discovered 12 support tickets yesterday on a plugin I had not realized we were not subscribed to, which I want to at least comment on to see if they still need help. I can't do this. It's a frustrating experience for me and clearly a poor user experience for the original poster or anyone else who encounters that thread with a similar problem. 4 4 5 Another option might be to auto-close them but add a button that allows them to be reopened by plugin contributors that sets another six 5 Another option might be to auto-close them but add a button that allows them to be reopened by plugin contributors that sets another six-month (or maybe a shorter time period) timeline before auto-close.