Moving from OTRS 2.4.7 w/ ITSM 1.3 to OTRS 3.0.1

[n0manarmy]

My OTRS setup was initially overcomplicated (by myself.) Having learned from multiple versions and changes, I've come to realize that the small help desk that I've setup OTRS to work for does not utilize a lot of the features I put in place. With the release of 3.0.1 I wanted to start fresh and new from our old setup with a new build on a new but with our old tickets and stats. Is there a suggested route for this or should I just bite the bullet and start completely fresh? Below is a list of what I have currently installed in the original and I've italicized what I don't want to carry over to the new installation (yet.)

Support 1.1.3 xxx
iPhoneHandle 0.9.5 xxx
FAQ 1.6.5 xxx

Calendar 1.9.4 xxx
FileManager 1.4.8 xxx
GeneralCatalog 2.0.3 xxx
ImportExport 2.0.3 xxx
ITSMChangeManagement 2.0.3 xxx
ITSMConfigurationManagement 2.0.3 xxx
ITSMCore 2.0.3 xxx
ITSMIncidentProblemManagement 2.0.3 xxx
ITSMServiceLevelManagement 2.0.3 xxx
Survey 1.2.4 xxx

[Mike_B]

Please understand that we don't yet have an FAQ package for OTRS 3.0.x, it will be due January 2011.

You could *in a test environment* just uninstall the modules you don't want, maybe you have to remove some freefield stuff as well, I guess it will be minimal. Then upgrade to V3, test, test, test, and go live

--
Mike

[ferrosti]

I am currently migrating from OTRS 2.2 with ITSM to OTRS 3.0 without ITSM.
I won´t switch before I have all customizations done, but the upgrade path works.

I have set up a new VM, cloned from the old system. I switched off cron to make sure it wont pickup mails or anything like that. Then I deinstalled all the ITSM packages and went for the 'usual' upgrade path as described in the UPGRADE files of the target version.
Afterwards I have written some 'decustomization' SQL file to reset all user themes to 'Standard', etc. Then have a look at the ITSM packages from the old version and copy the SQL commands from the deinstall part into your decustomization SQL file. It is important to keep the order of SQL statements in the same sequence as you have to deinstall your ITSM packages.
From this point you will be able to restore your backups on the 3.0 machine and do all SQL conversions by running your custom SQL files as well as the ones for upgrading.

I have written some shell 'batch' files and I make daily imports to the new system. It seems to work well.

[jtlatgf]

Mike,

I haven't seen any info on when the Calendar package is going to be released. I have installed 3.0.2 and LOVE it as well as our other agents but waiting for the calendar to be released before we put into production.

Is there a date for this package?

Thanks, Jeff

[jojo]

No, there is no planned date for the calender yet.

[Mothra]

Please understand that we don't yet have an FAQ package for OTRS 3.0.x, it will be due January 2011.

Is there a beta version I could use?

[jojo]

not at the moment, only CVS Check Out is possible

[Mothra]

not at the moment, only CVS Check Out is possible

Ah, I have the current CVS checkout - where do I find the FAQ module?

[jojo]

you have to checkout the faq, which is an extra module (FAQ)

[jonheese]

I see that FAQ is now available for 3.0.4, but Calendar is still M.I.A... Is it possible to checkout any unreleased Calendar code from CVS (i.e. is there a committed "beta")? If so, can someone point me to the CVS login info and any necessary information to go from source to package (eg. is compiling necessary, etc.)? Thanks.

Regards,
Jon Heese