There is a package intranet-jira, which is freely awaylable on our CVS server. It basically contains a Perl (our favourite integration language, replace with your preference :-) script, which uses the Perl JIRA::REST interface to pull data from a Jira server.
The status of the package is not yet "product", because it only worked with one customer, and may contain quirks. But you will the the idea from the code. I guess with knwledge of Jira REST interface and Perl you can make it run for your company in a number of hours.
For the final product version I'm still torn between two ideas:
Import all Projects from the Jira server and create the same projects in ]po[ with type "ticket container" or "agile" in the future (we are planning for a Trello type of project type).
Add parameters on a per-project base, so that only specific Jira projects are mapped to ]po[ projects.
I've got a slight inclination for 1., because it has less administration overhead...
We can collaboration on this one. Maybe you want to post here some advances if you should manage to get your integration going.
Cheers
Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hii,
How JIRA is integrated into project-open?
There is no portlet available for JIRA on project-open. Can anyone tell me how to access and how it works.
Regards,
Arjuman Banu.
Hi Arjuman,
Very good question!
There is a package intranet-jira, which is freely awaylable on our CVS server. It basically contains a Perl (our favourite integration language, replace with your preference :-) script, which uses the Perl JIRA::REST interface to pull data from a Jira server.
The status of the package is not yet "product", because it only worked with one customer, and may contain quirks. But you will the the idea from the code. I guess with knwledge of Jira REST interface and Perl you can make it run for your company in a number of hours.
For the final product version I'm still torn between two ideas:
I've got a slight inclination for 1., because it has less administration overhead...
We can collaboration on this one. Maybe you want to post here some advances if you should manage to get your integration going.
Cheers
Frank