Redmine

• Table of contents
• Objectives
  • More information
• Our story
  • Fist modifications

Objectives¶

1. Tell the world our experiences and works aroud Redmine.
2. Share with others our ideas, efforts and developed code.
3. Make our plugins as popular as possible and promote them as a regular part of the redmine's core project.
   h3. Who are we?

We are some IT professionals who work at Sadesi (a public company that belongs to Junta de Andalucia). We are happy of working in a company/government which is compromised with OpenSource and quality, Sadesi is compliant with ISO 9001, ISO 20000 (ITIL) and ISO 27001.

My name's Borja Pacheco and I want to clarify that I'm talking from a personal point of view, not trying to tell you the formal opinion of others (nor Sadesi, CEIC, neither Junta de Andalucia). I need to mention to María José Romero del Toro and Francisco José Quintero Morón, who are part of this project and without them, nothing wouldn't be possible.

If you want to contact me, please, use @Borja_Pacheco or http://es.linkedin.com/in/bpacheco, as you prefer.

More information¶

If you need further info about my company or our job, you could find it at:

• www.juntadeandalucia.es/innovacioncienciayempresa/sadesi/
• www.juntadeandalucia.es/organismos/economiainnovacionyciencia/consejeria/sgisi.html

Our story¶

Sadesi started to use Redmine as the main tool to manage our source development projects in the middle of 2010. Since that, we have use it broadly (some indicators: 29175 tickets created and 796 active users) and we have missed out some functionality.

Fist modifications¶

In a first approach we decided to make it ourselves and we modified several parts of the code to avoid tickets without one assigned persons (we don't want orphan tickets), we linked End-Date and Status to avoid tickets witough 100% completing, modified Gantt module, adapted Spanish translations, created a simple plugin-menu to facilitate access to other daily tools, made the tree-view plugin operative again and, finally, we made a custom application that uses redmine's data model, for being a bridge between redmine and our ERP (Navision).

This experience produced us a "bitter taste", because several difficulties:

• We didn't want to touch Redmine's core/kernel, but it was not possible in all cases. So we started to be very sensitive about redmine's updates & upgrades.
• Ruby, it's not our core business programming language. We feel more comfortable using Java or PHP.

But we learnt important facts:

• Redmine changes VERY quickly.
• Sometimes it's easier and cost saving, adapt our mind/methodology instead of modifying the tool.