Skip to main content
Skip table of contents

Release Notes v7.6

July 3, 2020

Server version may take up to 60 minutes to start for the first time if upgraded from the v7.0.6 or below due to DB schema update.

Important: ActivityTimeline has few infrastructure changes between v7.2.x and v7.3.0:

  1. Dropped support of 32bit servers starting from AT v7.3.0. Contact support if you are running AT on a 32bit server.

  2. New start.sh/stop.sh and start.bat/stop.bat scripts:

    1. Do not use them if upgrading from v7.2 or below and "atdb" folder is not in "<INSTALLED_LOCATION>/activitytimeline/bin/" folder as ActivityTimeline may not be able to load the previous data.

    2. Start ActivityTimeline in the same way as before or move "atdb" folder into "<INSTALLED_LOCATION>/activitytimeline/bin/" folder and then use the new scripts.

    3. You can use new scripts if you have ActivityTimeline configured to use external database like MSSQL, MySQL, PostgreSQL or Oracle DB.

  3. Upgraded underlying Tomcat to version 9 and JRE 8 u202


ActivityTimeline Cloud:  Released on June 23, 2020. 

ActivityTimeline Server: Released on July 3, 2020.


This version update includes the following enhancements:

  • Added new Team Panel functionality

  • Added possibility to expand the view in Plan module

  • Added possibility to display additional info on the issue bar

  • Improved dropdown fields to remove the limitation on the number of items in the dropdown

  • Improved method of loading Jira saved filters to allow loading of bigger number of Jira saved filters

  • Fixed worklog synchronization from Tempo Timesheets for multiple timezones

  • Fixed issue with the removal of Holiday schemes

  • Fixed issue with encoding of umlaut letters for German and other languages

Possibility to display custom field on the issue bar:

New Team Panel feature:

Dedicated documentation on this feature is available here: Team Panel

New option to expand the view of the Dashboard:

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.