New version of HESK: 2.4.1

[kabuc]

If I merge 2 tickets:
first ticket:
parent client message
staff answer

second ticket: (new ticket)
parent client message

I got:
parent client message
staff answer
second ticket parent client message

messages are ok, but last replier is still staff (but now must be "client"), and status is still answered (but now must be "not answered")

[Klemen]

Messages in merged tickets are sorted by date, not by parent/reply.

Will check statuses though for next verson, thanks for the heads up.

[Lisaweb]

Hey Klemen! Moved to a new business and went to install this for a client and saw how you updated it. Sweeet! Love the new features, esp. the "merge tickets". Thanks sooo much for your hard work!

[Klemen]

Thanks for the kudos!

[deserteagle369]

I plan upgrade from 2.3 to 2.4.1 with LDAP integration, I tested new install it works.

I did some customization on 2.3 so I need weeks to finish LDAP integration and upgrade, at the same time I need the server (2.3) still work for helpdesk and knowledge base usage.

I need some suggestions on my upgrade plan, if you can, help to check the process will go through well.

1. back up hesk 2.3 web files and database.

2. make a copy of hesk (web files and database) to a testing machine (also wamp)

3.import LDAP patch to a download hesk 2.4.1 by toristorHG

4. upload the hesk 2.41 (with LDAP) web files to testing machine

5. start upgrade from 2.3 to 2.4.1

6. apply my customization one by one

7. because the working server will run for weeks so there are new tickets and articles, what's the best way to update it?

my idea (3 options):

a. only allow new ticket and article, export new tickets and articles from database to sql file and import to 2.4.1 database by phpmyadmin
note:(if the table structure changed from 2.3 to 2.4.1, maybe the import will fail)

b. other support staffs continue update(create, tag,convert ticket to article, etc) on old version 2.3, empty the hesk_tickets and hesk_kb_articles table by "truncate" command keep the structure in 2.4.1 database, export xls from v2.3 database then import to 2.4.1 database.

c. do a upgrade on working server 2.3 to 2.4.1, so the script will update the database, then copy the web files from test machine (customization and LDAP finished) to overwrite the 2.3 web files in server.

any suggestion will be appreciate.