I’ve just started here at a shop using OTRS, and
I’m afraid they universally hate it.
I’m trying to sort out why and see if I can improve
how it’s setup and used so that
people stop trying to go around it and change that
perception.
We’re running 2.3.2 and hoping to move to 2.4 quickly,
but also looking
For get some quick insight on how to improve what I’ve
got immediately.
The area which I understand shows “system
messages”
Is full of messages about each ticket in the my queue
and completely obscures the basic queue view interface,
making
It harder for people to interface with the system overall.
Example of one set of message shown below.
Can you point me in the direction of any documentation to
explain why these show up
for every ticket and don’t go away until the ticket is
closed? How can I control it?
Is it because the users use OTRS in some particular way, or
a configuration issue?
Any help appreciated.
I’ve also another question on how best to use OTRS for
activities/tasks that aren’t
really from the user base, but internal tasks.
When in previous companies
we used bugzilla or JIRA as a ‘help desk’ ticket
system – it was easy to set tasks that were (internally generated)
and manage them together with user requests and add prioritization, deadlines,
etc . I don’t find any way thusfar to do this within OTRS, is it
just the wrong tool for the job? Any information you can point me to is
appreciated – Thank you!
-
Sarah Baker
mSpot Inc.
650-321-7000
Example system messages:
|
Ticket
2009092010000143: first response time is over (-18 minutes / 09/21/2009
08:30)! |
|
|
: Ticket
2009092010000116: first response time is over (-18 minutes / 09/21/2009
08:30)! |
|
|
: Ticket
2009091910000271: first response time is over (-18 minutes / 09/21/2009
08:30)! |
|
|
: Ticket
2009091910000164: first response time is over (-18 minutes / 09/21/2009
08:30)! |
|
|
: Ticket
2009091910000128: first response time is over (-18 minutes / 09/21/2009
08:30)! |
|
|
: Ticket
2009091810000139: first response time is over (-63 hours 57 minutes /
09/18/2009 16:51)! |
|
|
: Ticket
2009091710000061: first response time will be over in 23 minutes / 09/21/2009
09:12! |
|
|
: Ticket
2009091710000042: first response time is over (-60 hours 45 minutes /
09/18/2009 20:03)! |
|
|
: Ticket
2009091710000033: first response time is over (-96 hour 18 minutes /
09/17/2009 08:30)! |
|
|
: Ticket
2009091610000151: first response time is over (-108 hours 52 minutes /
09/16/2009 19:56)! |
|
|
: Ticket
2009091610000133: first response time is over (-112 hours 35 minutes /
09/16/2009 16:13)! |
|
|
: Ticket
2009091610000081: first response time is over (-115 hours 48 minutes /
09/16/2009 13:00)! |
|
|
: Ticket
2009091610000044: first response time is over (-119 hours 34 minutes /
09/16/2009 09:14)! |
|
|
: Ticket
2009091610000017: first response time is over (-120 hour 18 minutes /
09/16/2009 08:30)! |
|
|
: Ticket
2009091610000026: first response time is over (-120 hour 18 minutes /
09/16/2009 08:30)! |
|
|
: Ticket
2009091410000271: first response time is over (-157 hours 10 minutes / 09/14/2009
19:38)! |
|
|
: Ticket
2009091410000057: first response time is over (-168 hour 18 minutes /
09/14/2009 08:30)! |
|
|
: Ticket
2009091210000202: first response time is over (-168 hour 18 minutes /
09/14/2009 08:30)! |
|
|
: Ticket
2009091210000033: first response time is over (-168 hour 18 minutes /
09/14/2009 08:30)! |
|
|
: Ticket
2009091110000286: first response time is over (-168 hour 18 minutes /
09/14/2009 08:30)! |
|
|
: Ticket
2009091110000197: first response time is over (-231 hours 45 minutes /
09/11/2009 17:03)! |
|
|
: Ticket
2009091110000099: first response time is over (-237 hours 48 minutes /
09/11/2009 11:00)! |
|
|
: Ticket
2009091010000279: first response time is over (-254 hours 23 minutes /
09/10/2009 18:25)! |
|
|
: Ticket
2009091810000139: update time will be over in 29 hours 32 minutes /
09/22/2009 14:21! |
|
|
: Ticket
2009091710000131: update time will be over in 5 hours 46 minutes / 09/21/2009
14:34! |
|
|
: Ticket
2009091710000061: update time will be over in 35 hours 23 minutes /
09/22/2009 20:12! |
|
|
: Ticket
2009091710000042: update time will be over in 33 hours 14 minutes /
09/22/2009 18:03! |
|
|
: Ticket
2009091710000033: update time is over (-61 hours 48 minutes / 09/18/2009
19:00)! |
|
|
: Ticket
2009091610000151: update time is over (-63 hours 22 minutes / 09/18/2009
17:26)! |
|
|
: Ticket
2009091610000133: update time is over (-67 hours 5 minutes / 09/18/2009
13:43)! |
|
|
: Ticket
2009091610000081: update time is over (-70 hours 18 minutes / 09/18/2009
10:30)! |
|
|
: Ticket
2009091610000071: update time will be over in 26 hours 35 minutes /
09/22/2009 11:23! |
|
|
: Ticket
2009091610000044: update time is over (-85 hours 4 minutes / 09/17/2009
19:44)! |
|
|
: Ticket
2009091610000017: update time is over (-85 hours 48 minutes / 09/17/2009
19:00)! |
|
|
: Ticket
2009091610000026: update time is over (-85 hours 48 minutes / 09/17/2009
19:00)! |
|
|
: Ticket
2009091410000271: update time is over (-111 hours 40 minutes / 09/16/2009
17:08)! |
|
|
: Ticket
2009091410000057: update time is over (-133 hours 48 minutes / 09/15/2009
19:00)! |
|
|
: Ticket
2009091210000202: update time is over (-133 hours 48 minutes / 09/15/2009
19:00)! |
|
|
: Ticket
2009091210000033: update time is over (-133 hours 48 minutes / 09/15/2009
19:00)! |
|
|
: Ticket
2009091110000286: update time is over (-133 hours 48 minutes / 09/15/2009
19:00)! |
|
|
: Ticket
2009091110000197: update time is over (-138 hours 15 minutes / 09/15/2009
14:33)! |
|
|
: Ticket
2009091110000099: update time is over (-144 hour 18 minutes / 09/15/2009
08:30)! |
|
|
: Ticket
2009091010000279: update time is over (-160 hours 53 minutes / 09/14/2009
15:55)! |
|
|
: Ticket
2009091710000061: solution time will be over in 81 hours 23 minutes /
09/24/2009 18:12! |
|
|
: Ticket
2009091710000042: solution time will be over in 79 hours 14 minutes /
09/24/2009 16:03! |
|
|
: Ticket
2009091610000071: solution time will be over in 58 hours 1 minute /
09/23/2009 18:50! |
|
|
: Ticket
2009091410000057: solution time is over (-69 hours 28 minutes / 09/18/2009
11:20)! |
|
|
: Ticket
2009091210000202: solution time is over (-69 hours 28 minutes / 09/18/2009
11:20)! |
|
|
: Ticket
2009091210000033: solution time is over (-69 hours 28 minutes / 09/18/2009
11:20)! |
|
|
: Ticket
2009091110000286: solution time is over (-69 hours 28 minutes / 09/18/2009
11:20)! |
|
|
: Ticket
2009091110000197: solution time is over (-84 hours 55 minutes / 09/17/2009
19:53)! |
|
|
: Ticket
2009091110000099: solution time is over (-90 hours 58 minutes / 09/17/2009
13:50)! |
|
|
: Ticket
2009091010000279: solution time is over (-96 hour 33 minutes / 09/17/2009
08:15)! |