Thanks for pointing this out to us. This has been fixed in the latest release of Tempo Timesheets (7.16). Updating Tempo Timesheets to the latest version should resolve the issue.
We deliver new versions of Tempo Timesheets for JIRA Cloud upgrade to Atlassian. For every delivery, we create a page in our wiki listing all changes since last delivered version. We also create an upgrade request in the Atlassian JRA project.
The delivered versions are tested by Atlassian against the next JIRA Cloud versions and upgraded according to Atlassian upgrade schedule.
You can watch the Atlassian What´s New page (https://confluence.atlassian.com/display/AOD/What%27s+New) for all upgrade notes.
Please also watch our Timesheets Cloud Releases page (https://tempoplugin.jira.com/wiki/display/TT/Tempo+Timesheets+Cloud+Releases) for the latest delivered versions, as well as the status history for Tempo on JIRA Cloud upgrades.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events