I’m happy to finally release the first public version of my Invoice plugin for ChiliProject. This plugin can be used to create and manage invoices for customers using ChiliProject’s time entries. While this is the first public release, I’ve been using this code at Little Stream Software for all of my invoices since 2008.
Listing of current, old, and late invoice
Create and manage invoices
Automatic invoice creation based on time entries on a project
Invoice details based on issues
Payments to an invoice
Printable view of an invoice
To get a copy of the plugin, you can download it from my ChiliProject or get the source code directly from my GitHub repository
This version is pretty basic and specific to how I invoice in Little Stream Software, so I’ll be changing a few things in the next version to make it more generic. If you have an idea for a feature or want to send me some code, I’d be happy to have you open a new issue in the project tracker.
A bug fix update to my Redmine Rate plugin has just been released. It includes an important bug fix for the caching system. This version requires at least Redmine 1.0.0 and is compatible with Redmine 1.0.x, 1.1.0, 1.1.1, and ChiliProject 1.x.
Bug #5793 Cost cache not getting cleared when Time Entry attributes change
An update to my Redmine Rate plugin has just been released. It includes several bug fixes and a new caching system. This version requires at least Redmine 1.0.0 and is compatible with Redmine 1.0.x, 1.1.0, 1.1.1, and ChiliProject 1.x.
Last week I created another Redmine plugin to setup staging and testing servers with Redmine called Redmine Remove Membership. It’s a simple plugin that adds a Rake task to Redmine that will revoke the membership of a user from all projects. My client is using this on their staging server to quickly setup a limited test environment for their users.
This past week I created a plugin for one of my Redmine clients called Redmine Lock Users. It’s a simple plugin that adds a Rake task to Redmine to make it easy to lock all of the user accounts in the system.
We have been using this to lock down testing and staging servers. Since those servers have the same data as the production Redmine, any user could log into them on accident and not realize it. With this plugin we can lock all users accounts and only allow access for specific users.