Currently there is no README.md and description for this package. This file should be added.

Znuny4OTRSInput should be extended to show and hide fields via nice clean .Show('...') and .Hide('...') interfaces. Currently hiding fields is manually done in couple of extensions which makes bugfixing, developing and porting more difficult than needed.

After i receive a messages from specifc endpoints which uses utf-16 formats, this messages stay stucked in spool to reprocess.

I delete it directly from /opt/otrs/var/spool, but i dont think that is a right solution.

Hi,
The TimeUnits field is not supported in Znuny4OTRSInput.

Take care of AgentTicketBulk:
https://github.com/OTRS/otrs/blob/rel-4_0/Kernel/Output/HTML/Standard/AgentTicketBulk.tt#L90

Best regards,
Rolf

It should be possible to set and unset the mandantory state of an input field via .Mandantory('AttributeName', true | false)

Maybe it should be possible to get the Mandantory state via .Mandantory('AttributeName')

After refactoring the snippets (#4) the cheat sheet functionality should be reviewed and added to the readme etc.

The following Chinese translations of the ArticleTypes cause an error:

        'email-external' => ' (郵件-外部)',
        'email-internal' => ' (郵件-内部)',
        'note-external' => ' (備註-外部)',
        'note-internal' => ' (備註-内部)',
        'note-report' => ' (備註-報告)',
        'phone' => ' (電話)',
        'sms' => ' (短信)',
        'webrequest' => ' (Web請求)',

To rebuild/reverse the tree structure of an select field Core.Form.Znuny4OTRSInput uses the spaced indentation to detect the level. The listed indentations in the Chinese translation cause this code to go bananas and end in an endless loop. Because of the leading single whitespace a wrong level is detected which causes the loop to start. But since there are no other levels present the loop won't stop.

This advertisement should be removed:

We should remove that kind of stuff by outputfilter in future because of the lot of places where they are set.

When using the option RestoreDatabase for the UnitTest::Helper object and creating test tickets via its TicketCreate method, the helper tries to delete/clean up tickets that are not present in the database (because of RestoreDatabase option), throwing many "No such TicketID" error messages.

Hi,
if I try to install the repo I get:
Can't install/upgrade package, file var/httpd/htdocs/js/Core.UI.InputFields.js already used in package KIX4OTRS-8.0.5!

Any bypass?

In the Ticket Owner View is a special Owner handling, where the agent can chose between old owners and a list of all owners. Depending on which select field was used a radio button is set to the matching select field.

Znuny4OTRSInput should also set the matching radio button after setting a new Owner.

Trying to install Znuny4OTRS-Repo 5.0.2 package in the system having otrs5+itsm+kix4otrs return following error:

Can't install/upgrade package, file var/httpd/htdocs/js/Core.UI.InputFields.js already used in package KIX4OTRS-8.0.0!

Backend ERROR: OTRS-CGI-86 Perl: 5.18.2 OS: linux Time: Thu Jul 14 12:12:13 2016 Message: Can't install/upgrade package, file var/httpd/htdocs/js/Core.UI.InputFields.js already used in package KIX4OTRS-8.0.0! RemoteAddress: 172.17.0.1 RequestURI: /otrs/index.pl Traceback (756): Module: Kernel::System::Package::_PackageFileCheck Line: 3264 Module: Kernel::System::Package::PackageInstall Line: 546 Module: Kernel::Modules::AdminPackageManager::_InstallHandling Line: 1925 Module: Kernel::Modules::AdminPackageManager::Run Line: 1278 Module: Kernel::System::Web::InterfaceAgent::Run Line: 1042 Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler Line: 53 Module: (eval) (v1.99) Line: 206 Module: ModPerl::RegistryCooker::run (v1.99) Line: 206 Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 172 Module: ModPerl::Registry::handler (v1.99) Line: 31 System information: OTRS 5.0.6

The snippets are used very often and widely and were extended over and over. Currently there are a lot more tickets than there was initially thought or planned. The structure of the snippets should be refactored to be more ...

• structured (framework version, logic grouping, ...)
• efficient to use
• cleaned up (obsolet, redundant, ...)

Currently the following call has no effect:

Core.Form.Znuny4OTRSInput.Set('CustomerUserID');

This should be fixed

Expected behavior

Actual behavior

How to reproduce

1. default install otrs and Znuny4OTRS 6.0.50
2. open system config

Environment

• OS: CentOS 7.4
• Browser: any
• OTRS version 6.0.22
• Znuny4OTRS 6.0.50

Additional information

https://github.com/znuny/Znuny4OTRS-Repo/blob/master/Kernel/Output/HTML/FilterElementPost/Znuny4OTRSRemoveBSAdvertisements.pm#L478

Please reenable the support view in the admin interface:
Key Frontend::Module###AdminSupportDataCollector should be enabled.

thanks

Hi,

can you migrate the Znuny OTRS Repo and projects for the OTRS fork otobo.

I think it's not that much work. The OPM file must change in the XML tag OTRS_PACKAGE to OTOBO_PACKAGE. Adapt VERSION and FRAMEWORK from 6 ... to 10 ...

The XML config file which is coded as BASE64 must be adapted from the XML TAG OTRS_CONFIG in OTOBO_CONFIG.

Can you please support OTOBO. Thank you very much.