-
Currently only the space admin or the user admin can edit an item after it is saved. This patch enabled that also the owner of the trac (logged By) is able to edit the item. In practice it is possible to prescribe an there is no chance to edit it, except call the admin.
2009-11-06 09:30:33 UTC in JTrac
-
Here is a complete message file for german translations. Please add it to the repository.
2009-11-03 14:09:04 UTC in JTrac
-
Hmm thats really not a problem, isn't it? You export the data into an excel file (jtrac1) and than import it from the excel to your other instance (jtrac2).
regards, Manfred.
2009-11-02 14:12:00 UTC in JTrac
-
In the german version some functions (e.g. excel import) are not possible, because not all message keys defined are translatet and given in the german messages_de.properties. Wicket throws an exception if the key is not found.
As a work arround you can copy the messages_en.properties to messages.properties. The java ressource loader loads the ressource out of this (default) file, if any key...
2009-11-02 13:55:43 UTC in JTrac
-
For unix systems the table names in the beanshell script has to be in lowercase letters.
2009-10-05 09:13:27 UTC in JTrac
-
In the appendix you get a migration guide from HSQL to Oracle.
2009-10-02 11:30:02 UTC in JTrac
-
I use three installations of JTrac
1. For my own with a HSQLDB database. 2 Spaces more than 100 entries.
2. For a company (20 people) for issue tracking with a MySQL Database. One Space with more than 1000 issues.
3. For a company (100 people) with an oracle 10g database. Parameters: 50 Users, 10 Spaces, more that 1500 issues. The system was sucessfully migrated from an other system (tha.
2009-09-25 11:48:13 UTC in JTrac
-
Hi second_comet.
I added two patches for this problem:
1. Changing the hbm file as you described.
2. Changing the SQL statement, which is called to add the schema (from SELECT 1 to SELECT 1 FROM DUAL)
So there might be no problems anymore.
Manfred.
2009-09-25 11:37:15 UTC in JTrac
-
If you will change the database system to oracle you need to rename the comment column in the histroy table from comment to an other identifier e.b. jt_comment. In the appendix you get a patch for this.
2009-09-18 08:37:08 UTC in JTrac
-
Hi second_coment.
The database schema will be created automatically. You only have to create the database schema (called jtrac) and set the appropriate database settings in jtrac.properties in $jtrac.home.
2009-09-16 15:55:02 UTC in JTrac
