Steema Central

I tried to enter a year old issue in to the bug tracker and didn't see any info on it. How can I track these ( i.e TF77016692 ) ?

Hello,

I've just moved it to the public tracking system
TF77016692 was added before having a that public system.
http://bugs.teechart.net/show_bug.cgi?id=843

can you also move these over?

TF77016700
TF77016688

Hello,

sct wrote:can you also move these over?

TF77016700
TF77016688

Done!
TF77016700: http://bugs.teechart.net/show_bug.cgi?id=844
TF77016688: http://bugs.teechart.net/show_bug.cgi?id=845

So the Status: CONFIRMED, only means its understood and I'm guessing no work was done?

Hi,

sct wrote:So the Status: CONFIRMED, only means its understood and I'm guessing no work was done?

Yes, CONFIRMED means we could reproduce the problem here so we accept it. However, I can't tell when a ticket will be closed. There's a number of variables affecting the time to close an item in that list such as the complexity of the problem, the study of the possible collateral damages, the number of issues with a higher priority that claims our team attention,...

This is most certainly an appropriate response, though in the interest of using your API, issues like (TF77016692) where the browser just dies resulting in a bad user experience puts us in the position of shopping for another chart client. It's been close to a year since the issue was reported and is a show stopper for our release. Is that some way we can request urgency?

sct wrote:This is most certainly an appropriate response, though in the interest of using your API, issues like (TF77016692) where the browser just dies resulting in a bad user experience puts us in the position of shopping for another chart client. It's been close to a year since the issue was reported and is a show stopper for our release. Is that some way we can request urgency?

I'm sorry to hear that. We've been suffering some problems with our server that, as far as I know, have been already addressed.
I find TF77016692 here: http://bugs.teechart.net/show_bug.cgi?id=843

I see its flagged as "high importance" Is there an estimated turn arounded on that?

Hello sct,

This means this will be one of the first issues that be looked at. We expect to publish a maintenance release before the end of the month. We will try to fix it for the new version.