New Module: TicketChecklist

[reneeb]

When you identify several tasks in a ticket and you want to create a todo list, this module might be interesting to you...

http://opar.perl-services.de/dist/TicketChecklist

[RStraub]

Hey reneeb,

this looks like a great feature and I wanted to try it right away. Upon installation I noticed these error messages in the systemlog:

systemlog_error.PNG

The dev system is running on Ubuntu and OTRS 3.3.8.

Might that be an incompatibility with other installed packages?
Best regards,
Rolf

[reneeb]

Thanks for the feedback. Which DB do you use? There shouldn't be any incompatibilities with other packages...

[RStraub]

MySQL. In the welcome screen it reads:

Code: Select all

Server version: 5.5.38-0ubuntu0.12.04.1 (Ubuntu)

[reneeb]

Thanks, I will dig into it...

[reneeb]

Should be fixed now. Version 0.3.2 is out...

[RStraub]

Hey reneeb,

I'm impressed with the quick solution. The installation does work now, however we are still unable to use the checklist feature:
The new button "Checklist" appears in the menu, so does the Checklist widget on the right side. When we click on the checklist-button, the popup appears with the "plus" and "submit" button. If we click on the "+" button, nothing happens.
[Nothing = The buttons vibrate, but do not unfold any text fields.]

Tested with Chrome (Version 36.0.1985.125 m) and Firefox (29.0.1).

In the systemlog I can see this error message (which is unrelated to clicking the button, it happened only after the installation):

parser_error.PNG

and in the otrs error log these messages appeared:

Code: Select all

[Wed Jul 30 15:10:22 2014][Error][Kernel::System::XML::XMLParse][772] C-Parser:
not well-formed (invalid token) at line 15, column 83, byte 950 at /usr/lib/perl5/XML/Parser.pm line 187
!
[Wed Jul 30 15:10:22 2014][Error][Kernel::System::XML::XMLParse][773] XML::Parser produced errors. I use XML::Parser::Lite as fallback!

otrs.CheckModules.pl has all modules installed BUT HanExtra Encode, all but the mysql modules and Net:LDAP. The XML::Parser is installed in version 2.41

Best regards and in high appreciation of your work,
Rolf

[reneeb]

Strange...

Can you check http://134.119.13.102/otrs/index.pl?Act ... TicketID=1 ?

user: root@localhost
pwd: otterhub

(I will delete this jiffybox on Sunday)

Doesn't it work there either? For me it works...

The SystemLog doesn't show any problems with the installation.

[RStraub]

That works like a charm.

I'll try on a 3.3.7 box aswell on friday and see if the problem arises from 3.3.8

(and then step by step delete our other packages)

Best regards,
Rolf

[reneeb]

Maybe try an apache restart first...

[RStraub]

Ubuntu upgrade fixed the issue.

Thank you for providing a free version of this module, it looks very neat so far

[nextjp]

Hi there,

first of all, great feature! Thank you!

One problem tho: If tasks are written in Japanese, they appear as question marks in the "Ticket Checklist" for some reason. It looks like it's a character encoding problem, but I don't have this problem anywhere else when using OTRS, so it's more of a wild guess.

I hope you can help me out on this one! Thank you!

[reneeb]

Hi,

thanks for the report. I'll have a look at it today...

- Renee

[nextjp]

Hi,

glad I could help.
Another thing I've noticed is the widget itself. I don't know if that's intentionally, but drag'n drop doesn't work for the widget. Whatsoever, I like it up there, so just in case, I wanted to mention that.

Thank you for your effort!

[reneeb]

Yes, drag'n'drop isn't supported yet.

[reneeb]

Using Japanese Characters works for me. Can you check the collation of the database table?

[nextjp]

Sorry for being late with my answer, I didn't have access to my stuff over the weekend.

I checked the ps_ticketchecklist table and it appears to be the same as the entry in the checklist (see attachment). I noticed, it's not only the entries in the checklist which show up as question marks, but also the states within "Checklist Item State Management", if I choose to edit the state names with japanese names. So the problem persists within the whole module. One more thing which I've noticed during install, (some parts of?) the module installs into the "Custom" folder. I guess that's per design, but I just wanted to bring that up in case it's not.

[reneeb]

Which collation do the table have?

[nextjp]

Both, ps_ticketchecklist and ps_ticketchecklist_status collation is latin1_swedish_ci for whatever reason. The default settings are utf8_general_ci tho.

[reneeb]

that's strange as the addon doesn't define any collation. Do you use MySQL? Where and how did you define the default collation?

[nextjp]

Yeah, I use MySQL. Well, I never defined it, but that's what the home menu says after logging in, so I just thought it's worth mentioning. Don't really know how to proceed on this one, so I hope you can advise.

[reneeb]

http://stackoverflow.com/questions/1294 ... ble-column

http://forums.mysql.com/read.php?103,40536

How does your config (Kernel/Config.pm) look like? Did you migrate it from earlier versions of OTRS? Is there latin1 defined as db collation?

[nextjp]

I did migrate the OTRS to a new server, but both OTRS versions were identical. I searched for latin within the Kernel/Config.pm, but it isn't defined as db collation. The thing is, all other modules install just fine using the right collation. I tried to install some random modules after TicketChecklist and they did not choose latin1 as collation. It's kinda weird.

Either way, thank you for the link. I converted the character sets for ps_ticketchecklist and ps_ticketchecklist_status tables to UTF8 and it seems to work fine now. I assume I'm good to go, or is there anything else I need to adjust? Thank you very much for your assistance and sorry for troubling you with a problem which is probably on my side.