Forum

Upgrade from v5.0.6...
 
Notifications
Retirer tout

Upgrade from v5.0.6 to v5.1.4

15 Posts
2 Utilisateurs
0 Reactions
9,319 Vu
Martin
(@el-wallos)
Posts: 220
Active Member
Début du sujet
 
[#2791]

Hi

I'm preparing the migration from v5.0.6 to 5.1.4 (on Linux) and I have some questions:

When I test my migration, the first login page, after uncompressed the new gz file and start the apache, was the configuration login (with mysql port, user and pwd...etc), so my question is: during upgrade, a new db is created? is it normal to have this configuration login? the old db was deleted before the upgrade process? :silly:

Could you give me the right way to upgrade projeqtor?

Thanks.


 
Posté : 7 Déc PM 15:1212
(@babynus)
Posts: 14952
Membre Admin
 

It is because you created new folder with new version, so you lost some configuration.
But database will not be deleted (never done) nor erased.
What may happen is that you'll have brand new database besid previous one.

Bets way to migrate is :
- close application (through admin screen)
- disconnect all users (through admin screen)
- backup your database (even if migration is secure, it is a good practive to backup fatabase)
- copy (and not move) existing folder to backup files (this is not mandatory but may be a secure practice)
- overwrite exiting folder with new version (parameters will be preserved)
- reconnect as admin : database migration will be automatically applied
- re-open application (through admin screen)


 
Posté : 7 Déc PM 16:1212
Martin
(@el-wallos)
Posts: 220
Active Member
Début du sujet
 

Excelent, my upgrade was done successful!!!!

Thanks


 
Posté : 7 Déc PM 17:1212
Martin
(@el-wallos)
Posts: 220
Active Member
Début du sujet
 

I have a real work affectation on a task and a project, but the state was not change automatically to "in progress" on my new version v5.1.4.

What is wrong?


 
Posté : 7 Déc PM 17:1212
(@babynus)
Posts: 14952
Membre Admin
 

Several possibilities :
- you entered real work before 5.1 : the automatism only works when entering first work, on V5.1
- you did not define it to work this way (in global parameters)
- resource who entered first work did not have rights to change status to ongoing one


 
Posté : 7 Déc PM 17:1212
Martin
(@el-wallos)
Posts: 220
Active Member
Début du sujet
 

Thanks Babynus,

Several possibilities :
- you entered real work before 5.1 : the automatism only works when entering first work, on V5.1

I confirm you I'm working on v5.1.4.

- you did not define it to work this way (in global parameters)

What is the name of the parameter? Set to first 'handled' status?

- resource who entered first work did not have rights to change status to ongoing one

What is the name of the name of the permission?


 
Posté : 7 Déc PM 17:1212
(@babynus)
Posts: 14952
Membre Admin
 

What is the name of the parameter? Set to first 'handled' status?

Yes

What is the name of the name of the permission?

It's in the workflow definition


 
Posté : 7 Déc PM 17:1212
Martin
(@el-wallos)
Posts: 220
Active Member
Début du sujet
 

It is working (from assigned to in progress and from in progress to done) :woohoo: , but if I add left time on the real work allocation tab, the status will not change automatically to in progress, is it normal? 👿


 
Posté : 7 Déc PM 18:1212
Martin
(@el-wallos)
Posts: 220
Active Member
Début du sujet
 

It is working (from assigned to in progress and from in progress to done) :woohoo: , but if I add left time on the real work allocation tab, the status will not change automatically to in progress, is it normal? 👿

I saw on "List of types" --> "Activities Types" --> "Task " an option "Lock done", is it the cause of my problem?


 
Posté : 7 Déc PM 19:1212
(@babynus)
Posts: 14952
Membre Admin
 

I saw on "List of types" --> "Activities Types" --> "Task " an option "Lock done", is it the cause of my problem?

No.

I'm testing ...


 
Posté : 7 Déc PM 21:1212
(@babynus)
Posts: 14952
Membre Admin
 

Just tested : works fine.

Pay attention that :
- responsible should be set in most cases, otherwise status change is not allowed
- status is changed to first handled status, if activity is already in a handled status, there is no change.


 
Posté : 7 Déc PM 21:1212
Martin
(@el-wallos)
Posts: 220
Active Member
Début du sujet
 

Pay attention that :
- responsible should be set in most cases, otherwise status change is not allowed

Responsable was set.

- status is changed to first handled status, if activity is already in a handled status, there is no change

In my case, the problem is when the left time is 0, automaticaly the state was changed to done and after increase the left time to 5, the state was not come back to in progress.


 
Posté : 8 Déc AM 11:1212
(@babynus)
Posts: 14952
Membre Admin
 

In my case, the problem is when the left time is 0, automaticaly the state was changed to done and after increase the left time to 5, the state was not come back to in progress.

Just because there is no option to this 😉


 
Posté : 8 Déc AM 11:1212
Martin
(@el-wallos)
Posts: 220
Active Member
Début du sujet
 

Thanks Babynus, and it is a possible evolution for next release or you think it is not necesary?


 
Posté : 8 Déc PM 16:1212
(@babynus)
Posts: 14952
Membre Admin
 

Request recorded as Ticket #1892.
(but will not be included in next release unles someone sponsors it)


 
Posté : 9 Déc PM 19:1212
Share:
Retour en haut