Skip to content
Plugin to allow users to communicate with Redmine via Instant Messenger.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
app
config i18n in rails 2.2.2 Mar 6, 2009
db/migrate
lib/redmine_messenger
test
README.markdown
init.rb

README.markdown

Redmine Messenger

Plugin to allow users to communicate with Redmine via Instant Messenger.

Instalation

Install Xmpp4r library.

$ gem install xmpp4r

Download the sources and put them to your vendor/plugins folder.

$ cd {REDMINE_ROOT}
$ git clone git://github.com/mszczytowski/redmine_messenger.git vendor/plugins/redmine_messenger

Copy default messenger.yml to your config folder.

$ cp vendor/plugins/redmine_messenger/config/messenger.yml config/

Create jabber account for Redmine user and set its configuration in messenger.yml.

$ vim config/messenger.yml

Migrate database.

$ rake db:migrate_plugins

Run Redmine and have a fun!

Registration

Login to your Redmine. Go to page http://your_redmine_domain/user_messenger and fill Messenger ID field with your jabber id. Click save. You will receive verification code.

Add Redmine jabber account as your contact and send him your verification code. You should receive confirmation.

Type 'help' and read what you can do with it.

Help

All user related help is on page http://your_redmine_domain/user_messenger.

Features

  • timers
  • logging times
  • searching for issues
  • details of issue
  • timer status with logged time statistics
  • commenting issues
  • pausing/resuming timer when user become away/visible (configurable)
  • changing status of issue to 'in progress' while starting timer (configurable)
  • changing status of issue to 'finished' while finishing timer with ratio equalt to 100 (configurable)
  • assigning issues
  • notifications (configurable)

Issues

See Redmine Messenger LightHouse page.

Extending

To extend functionality create file app/messenger/NAME_messenger.rb. See app/messenger/issues_messenger.rb for usage example.

Something went wrong with that request. Please try again.