Tempo report makes extra requests when custom Worklog Attributes use Account

[Anson Hoyt]

When I add a custom Worklog Attribute to a tempo team report (select the attribute from Views menu), a request is made to retrieve the Account for each JIRA Issue, but the Account is already known.

While Tempo 7.6.3 delivered a major performance improvement, can the performance of this report be optimized further?

Background

We're using Tempo 7.6.3 on JIRA 5.2.7

Without showing any extra fields (all options unchecked on View menu), our Tempo Team report for May 2013 loads in 4.64 seconds, with the browser making 49 HTTP requests.

When the "Accounts" field is added, our Tempo Team report for May 2013 loads in 4.64 seconds, with 49 HTTP requests. No additional requests are made because the "Accounts" field is just part of the response to the existing request https://jira.example.com/secure/TempoTeamBoard!report.jspa?v=1&team=2&periodType=BILLING&periodView=PERIOD&period=0513&account=false

Performance Concern

We have two custom Worklog Attributes. Each dropdown varies on the Account, so that variable is included in the External URL.

• A dynamic dropdown "Type" loaded from
  https://example.com/{Account}/types.json
• A dynamic dropdown "Category" loaded from
  https://example.com/{Account}/categories.json

If we select "Type" or "Category" from the Views menu, our Tempo Team report for May 2013 loads in 7.88 seconds, with the browser making 162 HTTP requests.

There were 89 requests to retrieve the "Account" for each Issue:

• https://jira.example.com/rest/tempo-rest/1.0/worklogs/customFieldValue/FRSD-1/Account?_=1373374250966
• https://jira.example.com/rest/tempo-rest/1.0/worklogs/customFieldValue/OCS-1/Account?_=1373376974700
• etc.

Request

Can this performance be optimized further? A suggestion included as an answer.

(all times best of 3 page loads)

[Anson Hoyt]

Update Tempo Timesheets to use the "Account" data already available from TempoTeamBoard!report.jspa. This would eliminate 89 HTTP requests to tempo-rest, cutting 40% of the load time for this report.

While Account could be read directly from table#issuetable tbody tr.section.level-2 td.nav:nth-child(5), it would be better form to change the response a bit. Perhaps a data attribute:

<table id="issuetable">
<tbody>
<tr class="section level-2" data-fields="{account: 'FRSD'}">
  <td class="nav">...</td>
</tr>

...this would let you expand by adding more attributes to data-fields as needed

[Bjarni Thorbjornsson]

Thanks Anson.

You are absolutely right. I had spotted this optimization possibility and we are already looking into it.

Best regards,

Bjarni (Tempo development)

[Anson Hoyt]

Glad to hear it. Our management team was a little put off by the performance on some reports, but they'll be glad to see 97% optimization in 7.6.3 and additional optimizations are already on the way. Our development team is happy that this makes optimizations within our integrated apps less necessary.

[Viðar Svansson [Tempo]]

Tracked at https://tempoplugin.jira.com/browse/TT-42

[Anson Hoyt]

I'll vote+watch the issue. Thanks!