
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
I guess what I mean is that we ourselves communicate on the forum and create topics with errors. And the METAQUOTES team reviews these topics and reacts to them if they see a serious error.
It's like discreet video surveillance.
So everyone doesn't have to create an application in the service desk.
It's understandable, but still, I want to know for 100% that this error is responded to and fixed. If it are not going to fix it, that is, it is not critical, then get a reply that they will not fix it, then do not wait and look for workarounds.
I had a pending application in the SD, it was not fixed, although it was admitted as an error.
Just need some specifics - YES/NO.
This means one option:
We stop playing ping pong and wasting resources on step-by-step pulling details. We've been running a public service desk for 8 years and it's become clear that we can't go on like this.
We have our own work plans for many years to come and we are focused on developing them.
Little clarity on how the response will be)
I recall the CopyTicks epic. There were not a few bug reports with full playback code. Posted on the forum and repeated in the SD. The details were only sorted out in the SD and in a constructive way. It was felt that the developers had set themselves the goal of solving the problem with these tics at last. Whether the cause was in the SD or the forum, it is hard to say. At a rough guess, about 10% of the bug reports were my faults/weak understanding. In the end, after a few hundred requests (on the compiler and other topics) in the SD and bans, it was obvious that the requests were almost dead, so I stopped writing there. Left only forum posts.
Now custom characters require about the same attitude as they once did with ticks. I think with ticks it was just a coincidence that the urge to edit/message something turned out to be mutual. It's probably the same with other topics. And the channel of communication can be LS instead of SR, if only there was interest.
In general, since the CD has disappeared, it would be a good idea to create a new section on the forum for various MT-MQL bugs and appeals to the administration and developers. I've already got everything mixed up in a bunch of different sections. Better somewhere in the basement of the forum.
Another question is whether the administration and developers will find it necessary to respond. It's their personal business.)
Actually, it's a common practice. Well, almost.
Find the application number in the history and try to enter directly?
https://www.mql5.com/ru/users/fxsaber/servicedesk/closed/ХХХХХ
I haven't. I don't know the application numbers.
In general, since the CD has disappeared, it would be a good idea to create a new section on the forum for various MT-MQL bugs and appeals to the administration and developers. I've already got everything mixed up in a bunch of different sections. Better somewhere in the basement of the forum.
Another question is whether the administration and developers will find it necessary to respond. It's their personal business.)
Actually, it's a common practice. Well, almost.
Can you please tell me if the possibility to view closed applications in the SR will be returned? There was quite a lot of valuable information there (explanations) that I would like to have access to.
It was precisely because of the number of people who suddenly felt that it was our employees who had to waste their time asking questions about everything and everything that we shut down the public service desk. Service Desk has become a worldwide frenzy. Don't forget that we serve the whole world, not just the Russian-speaking part.
There is a huge amount of searchable information on this website. We have done our job, and in 7 languages. Now it is up to everyone to spend their time searching for answers to their questions.
Technical issues should be dealt with in a public forum so that every decision has a shoulder effect. Working with technical issues with 1:1 leverage in a closed service desk is economically unprofitable for any company with economies of scale (100-1000 clients is not scale).
We are now fundamentally changing the service processes on the website and automating everything we can.
Unfortunately, some of the old processes which used to be done manually have been put on hold for a while.
Which we automate and redo:
Critics:
That's just because of the number of people who suddenly felt that these are employees of our company should spend their time on questions about everything, we closed the public servicedesk. Servicedesque has turned into a complete madness on a world scale. Do not forget that we serve the whole world, not just the Russian-speaking part.
On this site a huge amount of information available for search. We have done our work, and in 7 languages. Now it's up to everyone to spend their time looking for answers on their questions.
Technical issues should be addressed at a public forum, so that each decision has a shoulder effect. Working with technical questions with a 1: 1 shoulder in a closed utility is economically unprofitable for any company that has a scale effect (100-1000 customers is not scale).
Now we radically change the maintenance processes on the site and automate everything that is possible.
Unfortunately, for a while some of the old processes, previously provided manually, were stalled.
What we automate and rework:
Critics:
Unfortunately, I do not speak Russian, but if I understand correctly, the publication and review of products is not available for some time. Correct ? Is there a schedule for how long when it will be available again? Thanks for informations.
Hi,
Hi to you too.
Banning a user on the forum automatically deprives them of tech support. Have you thought about it?
And You Hi.
Ban user in the forum automatically deprives him of his support. Have you thought about it?