Updating this ticket to reflect that is currently pending our next triage pass.

Updating status to appropriately reflect that this ticket is awaiting our next Triage pass.

Just updating the status on this to show that it's in our Triage queue waiting for our next pass. Thanks!

Hi Sebt,

As with the other tikets, unfortuantely this is currently sat in our Triage queue while our programmers and QA analyst work towards milestones on our other projects. Rest assured it will be addressed one way or the other though.

Cheers,

Lee

Thanks for raising this with us further Sebt. I can confirm that it's in our Triage queue and one I'll make a special note of as it's definitely quite frustrating. 

This sounds like an issue that has some deep roots but has often been difficult to replicate internally so any details we can get is always very important, especially if the end result is clear replication steps, videos, screenshots anything that will help us root out the cause.

I'm updating to status to reflect that it's awaiting our Triage pass and sorry that this has been pending for so long.

Hi Sebt,

As this is in our Internal Backlog and has never been marked as complete I should imagine this will next be reviewed with our Triage pass in 2019. At the moment our programmers are completely heads down on Project: Aftercare and WFTO will have to wait until we hit the appropriate milestones. Rest assured we've not forgotten and we will review this ticket. :) But if you've not heard something from us by say April then feel free to poke us again.

Cheers,

Lee

Moving into the Triage queue. We'll be doing a pass sometime in the new year. :)

Hi Vadim,

Due to the relatively minor impact of the issue this ticket is in our queue for review when we next do a triage pass on WFTO. This is currently scheduled for early next year. 

I'm sorry we can't address it immediately but as our team is currently entirely tied up with work on our next project we have to assign time to review these smaller issues. Rest assured though we've not forgotten about it! :)

I've added a new status to hopefully make this clear to customers who are waiting on ticket updates.

Cheers,

Lee

Hi GolanVI,

Very strange indeed. I'll put this into our review queue and raise it to the attention of our QA Analyst who will be able to ask the appropriate programmer for their thoughts on this issue and what the potential problems might be.

It's certainly nothing I've ever seen before and the error code looks particularly steamy. We'll try to get back to you soon.

Cheers,

Lee

This is probably too minor to address at this point, though perhaps it'll be an easy fix if we do. I'll put it into our Triage backlog for the next Triage pass :)