Activity
From 2007-03-24 to 2007-03-26
2007-03-26
-
21:53 Patch #214 (Closed): Switch from numeric issue ids to symbolic ones
- Switches issue ids from #1 to something like MYID-1
-
12:42 Defect #26: sqlite3 exception in db:migrate on AddChangesetCommitDate file when upgrading to last trunk
- The migration script is fixed, NULL is now allowed.
Thanks -
02:43 Feature #296: REST API
- I think that a minimum requirement should be to have an API that give full access at the issue level. This means access issues (CRUD), all the related models at least in read only mode (issues categories, etc..) and query support. This s...
2007-03-25
-
21:22 Defect #26 (Closed): sqlite3 exception in db:migrate on AddChangesetCommitDate file when upgrading to last trunk
- When trying to upgrade to the last trunk db:migrate aborts with this message :
% rake db:migrate --trace
(in /home/nc/travail/rails/redmine)
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environme... -
18:34 Defect #25: fetch_changesets broken
- Thanks.
Fix committed. -
15:50 Defect #25 (Closed): fetch_changesets broken
- If a project doesn't have any revisions between 1 and 200, fetch_changesets breaks. Suggest adding "unless
revisions.nil?" around the transaction. -
15:55 Feature #298 (Closed): Project to subproject relationship
- I suggest changing the project to sub-project relationship from one-to-many to a many-to-many relationship such that
a sub-project could belong to more than one project. -
08:17 Feature #286: SVN revision pseudo-automatically linked to issue
- SVN commits are now stored in the database. See:
http://rubyforge.org/tracker/index.php?func=detail&aid=9402%a
mp;group_id=1850&atid=7163
With a simple cron task, redMine can now scan repositories for
new commits. -
08:14 Feature #293: show initially the last x commits in SVN view
- SVN commits are now stored in the database, and added to the
activity view and the search engine.
New commits are automatically retrieved and stored when consulting
the repository in the app. This behaviour can be disabled by
uncheckin...
2007-03-24
-
07:57 Patch #213 (Closed): mail delivery workflow based
- Hi all,
As for the previous patch, I had the need to send email only to the user in charge for the new status of the issue and
not to the whole group of members for the project.
If you find it useful here is the patch. Suggestion ...