There was a time, when you could login into my website (this one) using your Google accounts. But, then it just stopped to work. Eventually, I’m happy to announce, that it works again!
To demonstrate, what is Redmine and how it works, in Mastering Redmine I create a special demo project. This project is about the book, so the latter can be considered to be about the former as well (yes, it’s about Redmine, but uses the project as a sample). And, for the second edition of the book… Yes, I work on its second edition right now, if you have not yet been aware. So, for the second edition I do the same – i.e., create a demo project on a demo Redmine installation. But, this time the installation is… live!
Currently, I use Atlassian JIRA on my job at Kayako – I use Redmine for my personal projects. And still I like Redmine more! But, what I like in JIRA is sequent numbers plus the project key in issue IDs. There are many benefits to such issue numbers, some of them are: a) you easily see how many issues the project has, b) it’s much easier to remember issue IDs (even if numbers are four-digit – not sure why, maybe because you follow numbers increasing), c) you always know, which project the issue is for. These are no way critical benefits for me, but one day I got interested – how the similar can be implemented for Redmine. So, I started to experiment… And eventually here goes the result of the experiment – the ISSUE-id plugin for Redmine!
There are many complaints, that Redmine is sending too many notifications and is missing functionality to configure them properly… So why then writing this plugin? I believe the problem is in what it sends. You can choose either to receive everything including issue changes, notes, Wiki changes, new messages in boards and so on or just issues. That’s either too much or too little.
Saying I’m just a user of a project. How do I know, when a new version is released?.. Yes, I can subscribe to RSS., but which RSS? News?.. Okay, I can do this. Since Redmine 2.5.x I can even watch news! Assuming, that there will be a news posted about the new release. But, what if not?.. Can I subscribe to files?.. No! Also, there can be no files in the project – users can get code from, e.g., Git. Maybe I can subscribe to versions?.. No! I can subscribe to activities RSS, but it has the same issue as email notifications – too much data! So I can’t know, when new version comes?!.
It’s absolutely common for a Redmine user to ask: How do I add custom HTML code to the Wiki content? Here by Wiki content users usually mean not just a Wiki page, as in Redmine a Wiki syntax enabled content is used everywhere (well, almost) – in project description, in issue description, in news, in comments, and so on. Anyway, normally, for Redmine such inquisitive persons get quick and definite answer: There is no way!..
As this is a common question, certainly, I used to ask it too. But, as I’m a Redmine plugin developer, I was able to “give” a different answer… Depending on the features, I developed, I used to implement some capabilities for embeding custom HTML code into different places of Redmine interface. There were no plan or design – I just implemented, what I thought at that moment can be reasonable and needful. Only after implementing those things I realized, that in several my plugins I implemented almost the same feature – the possibility to embed custom HTML code into the Wiki content. Luckily it was implemented in different ways…
To be more precise this was done in two my plugins – in Hooks Manager and in WikiNG. As some of these features are not foremost and, therefore, can be unnoticed and as the feature is commonly asked, I decided to describe its implementations in this article.
Github is the most popular online service for hosting and collaborative development of open source projects. And Redmine is the most popular personal and enterprise open source project hosting and management solution. So, no wonder, that these two systems are used together quite often.
Thus, Github’s Redmine service hook can be used to trigger fetching of repository updates by Redmine, when new commits are made to the Github repository. Unfortunately, it’s useless for the pure Redmine, as Redmine is not able to work with Github repositories directly (only through the local Git mirror, which needs to be created and updated manually)… Moreover, I am not aware of any solution, which could be used for this (even through the mirror).
Certainly, Redmine (especially its community) does much more to support Github. Thus, there is the plenty of tutorials describing how to mirror and keep Github repositories in sync for Redmine (e.g., this or this). Also there exist special plugins for making Github repositories easier usable under Redmine. The most noticeable such plugin is Github hook authored by Jakob Skjerning.
Till now I was trying to make all my plugins work under the common preselected set of recent Redmine and ChiliProject versions (thus, till recently they were: Redmine 1.4.x, 2.0.x, 2.1.x, 2.2.x, 2.3.x and ChiliProject 3.x). So, before releasing any of my plugins I had to test it under all such versions. Certainly, usually there appeared many compatibility issues, which I had to fix.
This approach generally failed… To support so many versions I needed much time, that I did not have due to different reasons – once the reason was the book, I was writing, another time it was stress, I had due to the severe crisis in Ukraine. The time comes and I write more new plugins, what, certainly, makes their support even more complicated. So, I believe, it’s the time to reduce the number of versions, I aim to support…
Also available in: Atom