Upgrading from 2.2.6 to 3.7.2 - Missing Issues
Sorry, I figured I would start a new thread since the issue is a bit different (although maybe related?).
When a user logs in, they see the open issues under the dashboard. When you click on the number, it says no issues found. If I drill down to a project, I'm seeing the exact same thing. It's almost as if the records are inactive. Is there a table I can look at? It's obvious that the software is calculating there are open issues so they aren't totally gone.
MStenz
· 1 |
|
Monday, January 3, 2011, 7:48:36 PM |
0
|
Please make sure that you have access to the project (view project in the security scheme). Also, make sure that you are member of the EVERYONE global group |
||||
|
0
|
That was it - Another note (yes, a slow upgrade process here), but it seems that the time tracking is missing when I did the upgrade. Upon further investigation, the gemini_timetracking table is empty whereas the old table timetracking has 4,000+ rows. So, I found the method in the upgrade script that handles this task and looks like it is getting an error: The INSERT statement conflicted with the FOREIGN KEY constraint "geminitimetrackingprojectidfk". The conflict occurred in database "GEMINI", table "Gemini.geminiprojects", column 'projectid'. The statement has been terminated. |
||||
|
0
|
Seems like you have some mismatch in projects for the time tracking, suggest you update the project id: update tempdb set t.projid = i.projidThat should solve it. |
||||
|
0
|
I'm running the part out of the upgrade script - SET IDENTITYINSERT geminitimetracking ON INSERT INTO geminitimetracking (entryid, projectid, issueid, userid, hours, minutes, comment, timeentrydate, created) SELECT entryid, projid, issueid, CASE WHEN u.userid IS NULL THEN -1 ELSE t.userid END, hours, minutes, t.comment, timeentrydate, t.created FROM timetracking t LEFT JOIN geminiusers u ON t.userid = u.userid WHERE issueid IN (SELECT issueid FROM geminiissues) SET IDENTITYINSERT gemini_timetracking OFF Should this be modified - (running the update tempdb fails)? |
||||
|
0
|
Sorry, auto complete in SQL killed my statement.... update t set t.projid = i.projid from timetracking t join issues i on t.issueid = i.issueidRun it before you run the part of the upgrade script. |
||||
|
0
|
Excellent! Thanks so much for the help! Should be good to go now! |
||||
|