heavy time in status calculation with Calculated Number Field (by JWT)

[Renni Verho]

Hi,

Tried to use Calculated Number Field (by JWT) to calculate time in status, but calculation takes way too long and is too heavy to use it in filtering and reporting.

One example of calculation "Math/Numeric Expression: timeInStatus("To Do")"

Filtering 2 issues with 6 time (12 values calculated) in status values took 70+ seconds in our test env. 

With out calculation field query took 1.24 sec 

Any proposals how to get it working / other solution to do math ?
One idea is to store dates when issue status have changed to custom field and after export do the math, but it would mean manual work.

[Thorsten Letschert _Decadis AG_]

Hi @Renni Verho ,

are all calculations performed as simple as the

timeInStatus("To Do")

one?

Calculating dynamic values definitely has a perceived/measurable impact on page loading, but on my staging environment, even with 20+ very complex fields, the loading times differ with a factor of 3 to 5 times - and not even close to 70 times like you've mentioned.

Are the technical prerequisites significantly lower than a 'usual' production system, e.g. is a dediacted database used instead of the built-in H2?

Cheers
Thorsten

[Renni Verho]

Hi, 

Yes, all calculations are like that example. 

Most of status are specific for that project. 

Technically our testing is close to production, only small changes accepted. Calculation should be much faster in testing as amount of users is much less than production. 

[Thorsten Letschert _Decadis AG_]

Hi @Renni Verho ,

unfortunately we're not able to reproduce any faulty behaviour with the information present.

Is the increase in loading time somehow linear to the number of calculated fields present? If it's applicable for you, I'd kindly ask you to file a support request at https://support.decadis.net/plugins/servlet/desk/ so that our support engineers could have a closer look.

Cheers
Thorsten

[Renni Verho]

Ill do request and lets add endresult here