The Atlassian Extension Spaces have been migrated to http://plugins.atlassian.com. These pages are now deprecated and will soon be deleted.

Tempo

Name Tempo JIRA Plugin
Version 2.7 - 2.7.1 for JIRA 3.12+
Tempo 4 version 4.1 for JIRA 4.0
Availability JIRA 3.12+
Homepage TM Software
Price See the new price model on our hompage
Documentation Administration, User, Videos
IssueTracking JIRA Tempo
Download JAR Try latest version of Tempo

Description/Features

It has often been said that simplicity equals truth. Indeed, simplicity was the motivating factor in the creation of the Tempo plugin.

TM Software presents Tempo, a JIRA plugin that integrates with your favorite ERP or billing solution, making JIRA a central hub for all business activities.When it

comes to issue tracking and project management, JIRA is fast becoming the industry standard.

Up until now, however, companies have been forced to rely on some form of supplementary tracking system in order to handle billing.
The Tempo plug-in solves the problem of multiple solutions by allowing staff to register the full spectrum of their tasks and billable hours through a single web-based interface.

In essence, Tempo unifies the previously disparate realms of issue tracking and issue billing.
To put it another way, Tempo is the bridge that connects JIRA with legacy enterprise solutions such as SAP and Microsoft Navision.

The graphic above distills the Tempo-powered workflow to its root elements:

  1. Import billing keys/attributes – Billing data originating in a 3rd-party solution is imported into JIRA via Tempo.
  2. Assign billing keys attributes to projects – Imported billing data is attached to a project.
  3. Registration of hours – Via Tempo, a project‘s billable hours are seamlessly updated and/or edited
  4. Export hours to billing system – At the conclusion of a given billing cycle, billable hours are exported to the originating billing system.

Keep in mind that billing data may travel bi-directionally at any juncture in the Tempo-powered workflow.
The basic steps listed here denote a typical usage pattern. However, in more precise terms, the workflow would be characterized as a continuum, and not a strictly linear process.

Tempo Highlights

Tempo enables users to:

  • Define and quick entry of Internal Issues
  • Display issues in a month, week or day view
  • Log work over a period of time & search work logs
  • Navigate in time to view previous and next period
  • Tempo administrator can view work logs & edit comments from all users
  • Tempo administrator can define / Open and Close a billing period
  • JIRA administrator can add and remove holidays
  • JIRA administrator can select groups of Tempo users
  • Bi-directional web service billing and reporting connector
  • Tempo administrator administrate billing keys from billing system

Usage & Installation

Tempo is easy to install with Zero configuration.
Tempo is Non intrusive as it does not modify or alter existing JIRA data.

To Install Tempo do the following:

  1. Download and extract the .zip file including the .jar file and documentations
  2. Shut down your web server
  3. Remove older.jar if you are upgrading
  4. Copy the .jar file to your WEB-INF/lib directory
  5. Restart your Web server

Screenshots




h2. Version History

Version Date Notes  
4.1 4. December 2009 This release focus was on improving the interface and take it closer to JIRA 4 along with few usability changes Release notes
2.7 & 2.7.1 24. November 2009 Bug fix and performance improvement Release notes
4.0.1 17. November 2009
  • JIRA war installation support
  • Link color in Tempo set as black instead of picking up the selected Link Color from JIRA
  • Text color in Tempo set as black instead of picking up the selected Header Text Color from JIRA
Release notes
4.0 26. Oktober 2009 We're proud to announce the release of Tempo for JIRA 4.0
With this release we have ported Tempo Enterprise to JIRA 4
Release notes
2.6 & 2.6.1 11. September 2009 Multible Tempo user groups and improvements in Billing Reports and Billing Key Manager Release notes
2.5 & 2.5.1 17. July 2009 Improvements in Billing Reports and added support for Oracle installations Release notes
2.4 & 2.4.1 26. June 2009 My Activity issues list and editable billing reports Release notes
2.3 29. May 2009 Billing reports can be generated in Tempo and round of usability improvements Release notes
2.2 15. May 2009 Usability improvements and standardizing localization of date formats Release notes
2.1 8. May 2009 First public release Release notes
2.0 15. February 2009 Releases 1.1 to 2.0 released for internal use at TM Software  
1.0 January 2008 First preview release at TM Software.  


Open Issues

JIRA Issues (18 issues)
Type Key Summary Assignee Reporter Priority Created Updated Status fixVersion
Improvement JTMPO-31 To view timesheet for the whole project group. Petur Agustsson Alexander Klimenko Major Feb 02, 2010 Feb 04, 2010 Open Wishlist
New Feature JTMPO-30 E-mail notification to employee with logged and missing time spent on tasks. Petur Agustsson Alexander Klimenko Major Feb 02, 2010 Feb 02, 2010 Open Wishlist
Improvement JTMPO-29 Possibility to filter tasks by Fix Version Petur Agustsson Alexander Klimenko Major Feb 02, 2010 Feb 02, 2010 Open Wishlist
Bug JTMPO-27 permission "work on issue" does not work for internal issues Petur Agustsson Michael Wagner Major Jan 21, 2010 Feb 01, 2010 Open Tempo 4.4
Improvement JTMPO-26 Set billing period to weekly or bi-weekly Sverrir Tynes Michael Wagner Major Jan 21, 2010 Jan 22, 2010 Open Wishlist
Improvement JTMPO-21 As a manager I would like to prevent writing down time spent on parent issues but rather on sub-issues Petur Agustsson None Major Nov 27, 2009 Feb 01, 2010 Open Tempo 4.5
Improvement JTMPO-19 allow staff users to close their own billing period Petur Agustsson Michael S. Major Oct 25, 2009 Feb 01, 2010 Open Tempo 4.5
Improvement JTMPO-17 Limit entries per day to no more than 24 hours Petur Agustsson Nigel Clarke Major Sep 11, 2009 Dec 07, 2009 Open Wishlist
New Feature JTMPO-13 maintain work account of employees Petur Agustsson Michael S. Major Jul 29, 2009 Jan 22, 2010 Open Tempo 4.4
New Feature JTMPO-12 allow definition of holiday groups (regions) Petur Agustsson Michael S. Major Jul 28, 2009 Jul 30, 2009 Open Wishlist
New Feature JTMPO-11 allow employees with different work hours per day Petur Agustsson Michael S. Major Jul 28, 2009 Jan 22, 2010 Open Tempo 4.4
New Feature JTMPO-9 As a manager I need to see a burnup chart for a billing key Petur Agustsson Sverrir Tynes Major Jun 08, 2009 Jul 30, 2009 Open Wishlist
New Feature JTMPO-8 As an employee I need to be able to sort issues by priority Petur Agustsson Sverrir Tynes Major Jun 08, 2009 Jul 30, 2009 Open Wishlist
New Feature JTMPO-7 As a manager I need to be able to view budget vs actual set value on a billing key in a billing report Petur Agustsson Sverrir Tynes Major Jun 08, 2009 Jul 30, 2009 Open Wishlist
New Feature JTMPO-6 As a manager I need to be able to set a budget for billing key (fixed quotes) Petur Agustsson Sverrir Tynes Major Jun 08, 2009 Jul 30, 2009 Open Wishlist
New Feature JTMPO-5 As a manager I need to be able to be able configure minimal time that can applied to issue for particular client Petur Agustsson Sverrir Tynes Major Jun 08, 2009 Jul 30, 2009 Open Wishlist
New Feature JTMPO-4 As a manager I need to be able to view staff utilization chart based of responsible manager Petur Agustsson Sverrir Tynes Major Jun 08, 2009 Jul 30, 2009 Open Wishlist
Improvement JTMPO-3 Administrators need to be able to modify worked hours vs billed hours on billing reports Petur Agustsson Petur Agustsson Major May 29, 2009 Jan 22, 2010 Open Wishlist

Labels

timetracking timetracking Delete
integration integration Delete
plugins plugins Delete
report report Delete
plugin plugin Delete
agile agile Delete
jira jira Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Nov 20

    peters cheng says:

    I have one question ,Tempo 4 is the release of Tempo for JIRA 4.0,  Tempo n...

    I have one question ,Tempo 4 is the release of Tempo for JIRA 4.0,  Tempo need DWR,  but JIRA 4.0 has removed it , how can  it works?