Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Tempo Timesheet Exception after Jira Upgrade


We are testing Jira Upgrade from Jira 6.x to Jira 7.12.3, Origin Jira  have Tempo Timesheet Plugin version 8.0.4, We installed Tempo Timesheet 8.15.1. However plugin is not working properly since when we try to configure Tempo throws the following Exception.


2018-11-16 17:02:12,357 http-nio-18080-exec-6 ERROR admin 1022x3073x1 dtweng /rest/tempo-timesheets/3/timesheet-approval/private/periods-with-pending-approvals [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: null
at com.tempoplugin.service.period.config.PeriodConfigImpl.getPeriodEndDateByStartDate(
at com.tempoplugin.core.Period.<init>(
at com.tempoplugin.core.Period.<init>(
at com.tempoplugin.core.Period$
at com.tempoplugin.view.TempoViewHelper.getPeriod(
at com.tempoplugin.view.TempoViewHelper.getPeriod(
at com.tempoplugin.view.TempoViewHelper.getBillingPeriodForApprovals(
at com.tempoplugin.view.TempoViewHelper.getPeriodByDate(
... 3 filtered
at java.lang.reflect.Method.invoke(
... 19 filtered
... 1 filtered
... 41 filtered
at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(
... 53 filtered
... 1 filtered
... 16 filtered
... 19 filtered
at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(
... 10 filtered
at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(
... 4 filtered
at com.atlassian.web.servlet.plugin.LocationCleanerFilter.doFilter(
... 26 filtered
at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(
... 24 filtered
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
at org.apache.tomcat.util.threads.TaskThread$
2018-11-16 17:29:39,228 Caesium-1-3 DEBUG ServiceRunner [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.plugins.authentication.atlassian-authentication-plugin]


Any idea how to get plugin to work properly.?


Thanks in advance.

Best Regards



3 answers

Hi Rodrigo,


Can you please inform us if you were following the update procedure as described on when updating Tempo.

The error you receive looks like an upgrade task did not run correctly. This can happen when you are updating directly from Tempo Timesheets 8.0.4 to the latest version. In that case, can you please create a ticket in our Tempo support ( so we can better assist you with fixing this problem.

Susanne Götz
Tempo team

Susanne, could you please explain this issue, and possible steps for resolution.  I have hit this same stack trace and can't figure out why.

We have restored an instance to a docker platform for testing merge migrations.  No version changes in the process, and selecting "Timesheets" leads to this error.

I've also notice the period configuration in the Jira add-on admin results in a blank screen without errors.


Adam Martin
Isos Technology

Hi @Adam Martin 

It might be useful to create a ticket for this in our Tempo support so we can better follow up on this.

Please add the versions of JIRA and Tempo you are using and the steps you have taken when restoring.



HI Guys

Also have the blank period configuration page, what was the resolution?

It was fixed? We have  little similar issue, we cant access the page with period configuration and when we try to open timesheets we got "something goes wrong"


/rest/tempo-timesheets/4/timesheet-approval/approval-statuses [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: The default period configuration was not found.
java.lang.IllegalArgumentException: The default period configuration was not found.

Hi @Erick Johanson 


Can you please create a ticket for this in our Tempo support system ( so we can better investigate this problem. 

It looks like it might be caused by an upgrade task that did not run correctly. 
If you were recently updating Tempo, can you please add information about the versions you were using before and which version you were updating to. 
The support zip file might also be helpful (

Susanne Götz
Tempo team 

API problem:/rest/tempo-timesheets/4/period-configuration,update the configuration,I resolve it!

Suggest an answer

Log in or Sign up to answer

Community Events

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

Events near you