Bug / Feature #2597
closedOTRS broken
100%
Description
Steps¶
What steps did you followed?
- Einloggen
- Ticket öffnen
- Replay / default
Observation¶
Fehlermeldung:
Core.Agent.CustomerSearch.AddTicketCustomer is not a function
(?)()@https://info.piratenpartei.ch/otrs/index.pl?ChallengeToken=87bea5b1d2783b27ec85e102666f1501&ChallengeToken=87bea5b1d2783b27ec85e102666f1501&Action=AgentTicketCompose&TicketID=5901&ArticleID=12843&ReplyAll=&ResponseID=1:624
Ready((function (a, b) {return new e.fn.init(a, b, h);}))@https://info.piratenpartei.ch/otrs-web/js/js-cache/CommonJS_69737867f59e69d962616c74362440ab.js:490
trigger([object HTMLDocument],[object Array])@https://info.piratenpartei.ch/otrs-web/js/js-cache/CommonJS_69737867f59e69d962616c74362440ab.js:36
trigger()@https://info.piratenpartei.ch/otrs-web/js/js-cache/CommonJS_69737867f59e69d962616c74362440ab.js:36
trigger([object Event])@https://info.piratenpartei.ch/otrs-web/js/js-cache/CommonJS_69737867f59e69d962616c74362440ab.js:36
Danach ist es nicht möglich ein Ticket zu beantworten.
Updated by corvus almost 14 years ago
- Status changed from New to 3
- % Done changed from 0 to 100
With the update to 3.1.1 the syntax of the configuration changed slightly an needed to be adapted.
Updated by corvus almost 14 years ago
- Status changed from 3 to 2
- % Done changed from 100 to 20
Das Löschen des js-cache hat nichts gebracht. Weiter recherche notwendig.
Updated by corvus almost 14 years ago
- Status changed from 2 to 3
- % Done changed from 20 to 100
Update auf OTRS 3.1.2 hat das Problem behoben.