Bug with feedback?

[dizietemblesssma]

I've noticed that none of my recent feedback bug issues have shown up on github. Is this just me?

Using Vortex 1.6.14

 

diziet

[Pickysaurus]

It doesn't show there automatically, it goes into a queue and is reviewed by Tannin. If the report hasn't got enough info to take any action on, it is discarded without reaching GitHub.

 

It's also possible that Tannin simply hasn't had time to review it yet. The focus is on bug reports over feature suggestions at the moment.

[Tannin42]

Usually I do try to assign feedback with too little information to an existing ticket with a canned response asking for more information.

 

The only tickets I close immediately are those with profanity or threads, those that would dox the sender if published and sometimes messages that we can't do anything about but constantly get reports for - so for example over the last weekend there was a bit of an api outage and the error messages in Vortex very clearly stated that it was a temporary server error yet we got dozens of message about that. I'm not going to spend most of my Monday replying to those individually.

 

But as Picky said: we get more feedback than I can reply to while still doing developing Vortex so feedback can pile up. So currently, if a request is already on the agenda or a bug already known I may leave the ticket in the queue as a reminder but not export it.

[dizietemblesssma]

This seems reasonable, but it does leave the sender in my position of not knowing the result of feedback. Could there be some sort of automated response so that a user knows that the feedback function has worked i.e. a response from the destination, not the programme?

 

diziet