Outside the original report, I don't see any mention of 'Average time in status' as being a problem; I'm treating this as only affecting the Workload Pie Chart.

The issue here is that there is no data to show; but that doesn't mean it should be an error. Instead, it should show:

No Data Available

to make clear that either the query needs to be reconfigured, or there's simply no data here.

Please fix, reporting on time spent on projects has got to be one of the most fundamental use cases there are. Is there any work-around or app that will resolve this request?

Just faced this issue (shall I really tell our users "No need to worry, there is just no more work to do when the gadget shows 'Internal server error'" ) too.

I can't believe that this was already reported in 2017

on add of gadget, this is prompted.

can not edit and configure the gadget.

I face the same issue while pulling a filter in Pie chart under confluence macros.

When can we expect a fix ?

I am getting this error, as well.  Trying to track Issue Type and Original Estimate on a specific project.

I am getting this error when I set "Time field to report on:" on "Original Estimate".
And values are setted for this field... So the update in the description is wrong.
Please, correct it or give me a true workaround, I need this gadget!

I am getting this error as well, no matter what I select in the available fields.

This error constantly occurs in the server and in the cloud version. I am filtering by project.
Please ignore this comment, it works now.

Why even show this gadget if Atlassian thinks this isn't priority? This bug was created back in 2017 and has no workarounds that has been specified. Assuming Verified status just means 'bug is accepted' since this is still reproducible.

+1 to me.  it looks to me a very obvious error which should be quickly fixed.

Well, I'm facing this issue too. Wanted to test some staff on test env, but this error appears after saving changes for gadget in dashboard.

Any word for Atlassian on this recently? I was really hoping to use this on my dashboard. Couldn't figure out what was doing wrong.

Agreed. This is an annoying issue. Please fix this.

+1 please fix. Balancing the team has become quite difficult.

Also, if anyone has any work-arounds for displaying rolled-up workload by estimate, that would be cool.

++ to that. I had to stop using Jira dashboards because of this, considering using another product because these are too unreliable 😢 

Please fix this.

Please fix this.

Impacting my team big time, currently can't track time spent on projects on any dashboards. Has this seriously been an issue for nearly two years without a fix?

+1 for the fix, no workaround yet, disappointed... here is my filter:

agree with comment from ipulgar that problem exists only in case filter returns tickets with no time estimation and at the same time Time field to report on  is set to one of Current Estimate or Original Estimate

@atalssian this one should be easy to fix

Just encountered this issue today. Would be great to receive an update on upcoming fix. 

We still have the same issue. Any update when it going to be fixed, guys ?
Thanks 

I have the same issue. When is this going to be fixed?

I had the same problem - mine was solved in the way of a mistake i made: I didn´t filled out estimated time, but story point estimate...so there was no data and therefore nothing that could have beed displayed.

I seem to be encountering this with the normal pie chart.

I have the same filter choice set up for another gadget (filter list) which is displaying perfectly. 

This was fine on friday, only affecting me this morning.

+1

Please check this, as it seems to be the only way to have a percentage based on velocity chart..

I started seeing this issue just this week. It seemed to work fine before that. I'm a new customer and don't have any real tickets in the system yet but will in the coming weeks. Sure wish this would be resolved soon.

From my end, this error seems to be thrown when no issues with timespent/worklogs had been retrieved by the filter/project.

When fixing this issue, please address JRACLOUD-67296 at the same time. JRACLOUD-67296 is directly affecting legibility of these charts.