ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Tagging (Feature #720)

Added by Eric Davis at 2011-11-18 07:05 pm. Updated at 2011-12-02 12:40 am.

Status:Closed Start date:2011-11-18
Priority:Normal Due date:
Assignee:Eric Davis % Done:


Target version:3.0.0
Remote issue URL: Affected version:


This will add a tagging backend so datatypes can use them. This will not include tagging any existing datatypes, only the API.

Related issues

related to Feature #139: Tags for issues Open 2011-02-04

Associated revisions

Revision 8fc2b727
Added by Eric Davis at 2011-11-25 08:23 pm

[#720] Add acts-as-taggable-on gem and migration for tag support

As per the gem docs, 2.1.0 is the last Rails 2.x compatable version

Revision f179fea7
Added by Eric Davis at 2011-12-02 12:58 am

[#720] Use = to show the explicit dependency


Updated by Eric Davis at 2011-11-18 07:06 pm

Note: Used acts-as-taggable-on for and it was good a year ago. Need to do a quick review of whats available.

Updated by Eric Davis at 2011-11-25 07:27 pm

A lot of tagging libraries have been abandoned since I last looked. acts-as-taggable-on is still maintained, works with Rails 3, and provides everything we need at the moment.

Pull request:

The code to add tagging to a model is simple, this just added tagging to issues.

 1diff --git a/app/models/issue.rb b/app/models/issue.rb
 2index 233e2bb..e6eed56 100644
 3--- a/app/models/issue.rb
 4+++ b/app/models/issue.rb
 5@@ -14,7 +14,7 @@
 7 class Issue < ActiveRecord::Base
 8   include Redmine::SafeAttributes
10+  acts_as_taggable_on :tags
11   belongs_to :project
12   belongs_to :tracker
13   belongs_to :status, :class_name => 'IssueStatus', :foreign_key => 'status_id'

Creating a usable user interface will take a bit more code though, which should be discussed in #139.

  • Status changed from Open to Ready for review

Updated by Felix Schäfer at 2011-11-25 08:05 pm

Looks good to me, Holger too. Just had a look at the gem though, and it seems 2.1.0 will be the last to support rails 2.3? I think we should add an explicit = to the version string then and add a comment why we want to stick to that version.

Updated by Eric Davis at 2011-12-02 12:40 am

Merged the pull request into unstable and added the '=' gem requirement.

Now it's time to start adding a user interface for tagging. Yay!

  • Status changed from Ready for review to Closed

Also available in: Atom PDF