Previously I wrote Integrating Atlassian JIRA using Tempo Plugin - Part 1 - here is part 2.
How to integrate - an aid to development and testing
An important part of integration is of course the development and testing! The Tempo API provides 2 important features to aid developers during development and testing:
- Specifying the format=testData parameter to GetWorklogs creates an XML that can be used as input to UpdateWorklogs
- Example: http://localhost:8080/plugins/servlet/tempo-getWorklog/?dateFrom=2011-01-01&dateTo=2011-01-31&format=testData
- Opening http://localhost:8080/plugins/servlet/tempo-updateWorklog/ in a browser opens a simple page where the developer can paste update XML and POST to Tempo
How to create a worklog "warehouse"
Some of our larger customers (including Origo itself) need much more powerful reporting than Tempo or any other JIRA plugin provides. These customers use the Tempo API to populate a "warehouse" and do their data crunching on the exported data with specialized reporting tools. Tempo eases this integration by adding several parameters to GetWorklogsthat add information to the worklogs. Examples:
Tempo also provides 2 additional functions that can be useful when populating a "warehouse":
- BillingKeyList: returns a detailed list of all billing keys (expenditure items) in Tempo.
- HolidayList: returns a list of all holidays specified in Tempo. This is useful when calculating for example workload and staff utilization.
How to create (simple) reports based on billing key (expenditure item)
The Worklog Report function returns an XML with "cooked" data that is ready to be rendered as a nice report. This can be quite handy for organizations that need to create worklogreports as a part of an invoice.
Custom made reports with XSL
A Tempo customer has generously shared his version of Tempo reports that he creates with some PHP and XSL. You can download his reports here and start extending/customizing for your needs.