The importing of Jira issues into orderlines is working nicely. Off course it is entirely possible to tag a Jira issue with more than one label and thus have the same issue appear in more than one project in LibrePlan, but we blame that on the stupidity of the user 🙂

We are now working on building a monthly timesheet filled with Jira worklogs. We link the Jira userid with the id of the resource in LibrePlan. Off course it is possible that the resources does not yet exist. Off course we could auto-create it, but actually we can’ t because, even if we know the username from Jira, who will tell us what part is the firstname and what part is the lastname? So we decided to build it as follows: if a resource exist all is fine (duh), otherwise we will display an error message. It is a non-fatal error, so all correct worklogs will be stored, or replaced if they already exist.

If this seems to work fine we will supply the patch after making some unit-tests and documentation. After that we will go ahead with some more wishes we have. One of them is sending the timsheets to our timesheetprogram from Aenova using Soap. Somehow there are still hills to climb there.

We will keep you informed. Till next time.

Hello all,

Intro

(skip this if you are not interested 🙂

Let’s start with a very small introduction: I work at the st. Antonius hospital in the Netherlands as head of the internal software development department. We build internal software and work on a lot of different projects. What I needed was a good project management tool so I looked at a couple and decided to go ahead with LibrePlan. I developed a training manual, trained some of my people how to sue it and now we plan projects in LibrePlan.

We also use Jira for our bugtracking and a dutch program called Timn Enterprise for our worksheets.

Functional design

The connection should work like this:

1. We use labels in Jira to tag issues that belong to the same project.
2. I want to be able to start a new project in LibrePlan and have it import all the issues with the same label into the Work Breakdown Structure (WBS) so I can plan the work and assign resources to it.
3. I want to have my people who work on an issue to enter worklogs in Jira and use that information to get an indication of the project progress in LibrePlan.
4. I want the worklogs in Jira to be send to Timn to prepopulate the worksheets and I want the approved holdays out of Timn into LibrepLan as resource unavailability.

I thought it would be cool of we could connect the three programs (Jira, LibrePlan and Timn). One of my guys is good in Java so I asked him to start on this venture since he was in between other projects.

First steps

At first Miciele build a configuration option into LibrePlan to enter Jira url and login credentials and a test button so you could see it the connection was succesfull.

I wrote about this before on Facebook:

1. Configuring the connection: http://i760.photobucket.com/albums/xx242/kwoot/jiraconnector.png
2. The ability to enter a label in the general data tab of a project: http://www.facebook.com/photo.php?fbid=4162614776565&
3. A simple import of some tickets into a project:  http://www.facebook.com/photo.php?fbid=4162612936519&set=o.270582536333485&type=1&relevant_count=1

Now it was time to really build something.

Progress

It has been some weeks now that Miciele Ghiorghis has been working on the connection between Jira and LibrePlan and it is time for some new screenshots:

We found out that Jira has great REST and SOAP interfaces, but can not give (yet) us a list of all labels used so we could build a nice autocomplete inputbox. After some debate and a supportticket at JIra we decided to build a simple PHP script that does a simple SQL statement (“select distinct label from label”). At the moment our wish is a feature request so we kindly ask you people to vote for it! 🙂 https://jira.atlassian.com/browse/JRA-29409

Using the PHP script we have a nice autocomplete form to enter the label.

Currently it looks like this:

We moved the Jira sync button to a better place on the same page:

We will put the chosen label into the external code field, just not yet 🙂

There are 2 changes in the WBS screen below.

1. The amount of hours is read-only because we will start with a simle one-way sync. So if you want to update the hours you can do that in Jira.
2. The “Code” column not only shows the Jira issue-id, but you can click on it and jump straight to Jira! (pretty cool we think)

Next steps

Next we will import the Jira worklogs to get a progress indication in LibrePlan.

If that all works we will finalize the first phase and submit a patch to the LibrePlan community for inclusion in the code.

Phase 2

Our phase 2 will revolve around making the connection to our time registration application Timn enterprise using SOAP. That is, if we get support on this from the supplier. We’ll see.

Goodbye, and until the next update! 🙂