Tempo Timesheet slow performance for Internal Issues

[Robson Lunardelli]

System:

• JIRA: 7.8.1
• Tempo Timesheets: 8.12.1

- Question -

What can be done to speed up tempo when logging work to an issue that has an "Internal Issues" link setup?

- Explanation -

We're experiencing a lot of lag and slowness when we try to log work against an "Internal Issue". You fill the form to log your work and the spinners just spins. After some time you get an error that says: "Add hours failed - Service timed out - Please try again". But when you click on the cancel button and refresh your page, the work you've just logged shows up in your timesheet.

[Susanne Götz _Tempo_]

Hi Robson,

can you please give us some more information about this. 
Is this problem only connected to Issues listed as Internal or can you reproduce this also on other issues.

Does this issue have a lot of worklogs or a long history (you might then be affected by the problem reported in https://jira.atlassian.com/browse/JRASERVER-45903).

In case this is an issue with less than 100 entries in the History, can you please create a ticket in our Tempo support (https://tempo-io.atlassian.net/servicedesk/customer/portal/6) so we can better investigate this problem.

Regards,
Susanne Götz
Tempo team

[Robson Lunardelli]

After closer look, it does seems to be related to the internal issues with more than 100 entries.

The issue you've mentioned has been opened for quite some time. Any idea if it will be worked on?

[Susanne Götz _Tempo_]

I do not have any information when this will be worked on by Atlassian, but adding your vote to the Issue might be useful.

[Mark Gaz]

This became a major issue for us with hundreds of people booking to some internal issues.

Our solution, which has worked for us, is to create new versions of these tickets every 6 months, and get people to book to the new items.  A bit of pain once every 6 months, but it minimises the impact significantly.