Integrating Tempo with your business solution – part 2

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:

  1. Specifying the format=testData parameter to GetWorklogs creates an XML that can be used as input to UpdateWorklogs
    1. Example: http://localhost:8080/plugins/servlet/tempo-getWorklog/?dateFrom=2011-01-01&dateTo=2011-01-31&format=testData
  2. 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 TM Software 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:

  • addBillingInfo
  • addIssueSummary
  • addIssueDetails
  • addWorklogDetails
  • addUserDetails

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.

Related Posts

Tags: , , , ,
Bjarni is the team Scrum Master and master of agile best practices. Bjarni has been involved with the Tempo Plugin team since its start few years back, and is a tremendously experienced developer. He has been responsible for the integration of API elements with our key architecture. Bjarni has over 15 years of experience in Java and web application development. Outside of work, you’ll find Bjarni climbing mountains or hiking in the wilderness.

3 Responses

  1. […] You can read part 2 here: Integrating Tempo with your business solution This entry was posted in How To, Integration and tagged JIRA, worklog by bjarnit. Bookmark the […]

  2. Amazing link!

    Thanks, very helpful, since we are creating a few validations on worklogs (to uset maxHourPerDayPerUser/Group/Role).


  3. We want to set-up integration between Jira and SAP ECC. Is there anyone that has done the same?
    Interfacing will be Bi-directional:
    -> Customer data going from SAP to Jira (SAP is master)
    -> Contract, Engagemement Order, and operation/activity data going from SAP to Jira (SAP is master)
    -> Work Log Data going from Jira to SAP. (Containing Key Engagement Order Number, Operation ID, SAP Employee ID, Number of hours worked on the issue and a short work log note)

    Does anyone have some documentation and/or examples how you do it?
    Thank you for any feedback!

Leave a Reply

Plan, Budget, Track & Adapt with Tempo for JIRA.

Subscribe to our blog

Get the latest posts delivered to your inbox:

Thank you for signing up!

Please check your email to confirm your subscription.

Select the Tempo products you'd like to hear about:

Tempo Planner Tempo Budgets Tempo Timesheets