Quote from IBj:
---------------------------------------------------------------------------------------------------------
Initially, the design relied on clients closing tickets when they were satisfied. It turns out that people weren't closing tickets and this was creating a clutter of theoretically open issues on the internal interfaces. The clutter in turn made it hard to identiofy new issues.
So we instituted a cleanup of old items and closed them ourselves. In the meantime, we added a dual closure algorithm which allows us to keep our side clean but leaves cotrol with the client. It works as follows.
if CSR thinks the issue/question has been answered/resolved, he/she is permitted to close it. This does not set a true closed state (CLS), but rather a Pending Closed state (visible to the client as PCLS). Pending closed tickets drop from the active view of the CSR.
However, on the client side, the following happens: if the ticket is replied or added to by the client, it is automatically re-opened and becomes again visible in the 'In Progress' view internally. If the ticket is ignored or otherwise not touched by the client for 7 days, IB presumes the client is satisfied and a program will automatically run and set the full closure state.
---------------------------------------------------------------------------------------------------------
No, it is incorrect.
As said by
mattm, they may forcefully close clients' tickets at their discretion without allowing the ability to re-open them. When it is deleted, it is not viewable in the "inactive" tab. The tickets are simply gone.
Please re-read the following official reply from
mattm:
---------------------------------------------------------------------------------------------------------
The web ticket system is provided as a service to our customers. Should this service be abused or should the number of submitted tickets cause inefficiencies in the customer support group, these tickets may be forcefully closed without allowing the ability to re-open them.
---------------------------------------------------------------------------------------------------------
Quote from IBj:
---------------------------------------------------------------------------------------------------------
Closed tickets can be reopened for up to 7 days. We don't allow indefinite re-opening because clients were re-using an existing ticket to ask an unrelated question, which prevents us from routing tickets to the right team. For example, clients would ask a trade desk question and then later ask a funding question. These service teams are fully disjoint but the recycling of the old ticket made it hard to route the funding question properly.
---------------------------------------------------------------------------------------------------------
Yes, this is reasonable. However it would not be the case when IB forcefully deletes the ticket.
Quote from IBj:
---------------------------------------------------------------------------------------------------------
One of the biggest hurdles we have had in developing this system is anticipating clients use (or misuse). Deisgn elements that I, as architect, presumed would be the best for the workflow, prove problematic when people do things like reuse old tickets for new questions. I dont know why they do; I wouldn't were I a user; but it is this way and I don't think retraining clients is productive or realistic.
---------------------------------------------------------------------------------------------------------
It is because your staff still promotes such kind of workflow.
Let's talk about my case. When I deal with bug tracking and reporting system, it is normal to contain one bug per issue. I do so by sending one bug per ticket. Also when I have questions, say, there are 3 questions. The first one is about hotkeys. The second one is particularly for booktrader. The third one is sending and modifying orders. Instead of lumping all questions together as a ticket, I send each question per ticket.
Nevertheless I am accused of abusing the ticket system and ask me to lump the questions and bugs together as one ticket. I do so by closing other tickets and re-send them by replying them in the first ticket.
Quote from IBj:
---------------------------------------------------------------------------------------------------------
If the inquiry was related to a problem you actually experienced that needed correcting, then please give me an example by E-T email. We can only fix a problem if we can find a specific case to test.
Bug reports get entered into a defect tracking system which feeds into the development department. As bug fixes, and suggestions, can be 1 hour to forever, there really isnt a response method. We fix bugs depending on their priority but there isn't really a great way to inform clients about when that happens.
Please enter suggestions into our new features voting system. That is the best way to get your ideas to the programming queue.
---------------------------------------------------------------------------------------------------------
What's the best way to report possible bugs?
Should I send via poll system or ticket system?
I ask this question because your staff,
mattm, seems to suggest me to file bug report in poll system.
I have filed a bug report. Then
mattm replied me as follows:
---------------------------------------------------------------------------------------------------------
This setting cannot currently be adjusted in the TWS.
One of the advantages of being an IB customer is that we listen to our professional customers as we continue our never ending quest to lead the industry with the most advanced trading technology. In order to systematize your requests we are adding a new permanent feature poll that allows you to suggest new TWS enhancements and to have other customers vote on the enhancements. We will do our best to prioritize those requests with the most number of votes. To nominate requests and to vote, visit our new TWS Voters Poll page, to learn how to sign up for a Voter ID and password in order to add your voice to our programming queue.
www.interactivebrokers.com/en/general/poll/poll.php?ib_entity=llc
---------------------------------------------------------------------------------------------------------
I don't understand why he calls it "setting", but he copied this reply for a bug report. What does it imply? Should a bug go to the poll system? I'm confused.
After all, I would suggest a bug tracking and reporting system like
https://bugzilla.mozilla.org/ (the software is called bugzilla
http://www.bugzilla.org/ ).
Reasons:
- I found many bugs in TWS. It would be crazy to lump all bugs together as one ticket.
- other people can view the bugs
- Reduce bug duplication: when people see the bug, they would not sending the same bug over and over again
- search the bugs
- easy to keep track on the bugs
Quote from IBj:
---------------------------------------------------------------------------------------------------------
There is no "MaxTicket algorithm". That incorrect assumption is leading to false conclusions I think.
---------------------------------------------------------------------------------------------------------
Only 9(?) tickets can be displayed. You can issue more tickets, but the older ticket will be pumped out of the system. What's more, I am accused of abusing the ticket system because I sent too many tickets (as I have about 9 tickets opened at one time).
Please see the following official reply from
mattm:
---------------------------------------------------------------------------------------------------------
Should this service be abused or
should the number of submitted tickets cause inefficiencies in the customer support group, these tickets may be forcefully closed without allowing the ability to re-open them.
---------------------------------------------------------------------------------------------------------
Quote from IBj:
---------------------------------------------------------------------------------------------------------
Last comment:
Much has changed in the Web ticket interface over the last 2-3 months. If you have not used it recently, your experiences and opinions may be outdated. As with every aspect of IB's business model, we release systems, constantly work on them and improve them, and we listen to constructive commentary. That is as true with service technology as with the brokerage system technology.
---------------------------------------------------------------------------------------------------------
This incident happened in less than a month.
I have PM you, so you can follow up the issue.
Thanks for your help in advance.