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.
Hi @Renni Verho ,
are all calculations performed as simple as the
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?
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.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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