This can be closed.

This can be closed.

We also now got some dashboards displaying the preferences error, for pie charts. Also for some resolved vs new and aging charts we got a different error stating invalid project or filter. We just discovered the problem is the filter. It was only visible to the filter creator. We changed it to share with everybody in the project and now the gadgets show ok. So Jira 6.4 filter/gadget permissions have become stricter, because thes problem we didn't have with 6.3.

Same here, we upgraded from Version 5.x to 6.4.11 and now some PieCharts show following message "Unfortunately, one or more of your preferences are now unavailable. Please update your preferences, or remove gadget by clicking delete from the title bar above. An error occurred while generating the response." and the filternames changed to "filter-12345".

We see another problem after upgrade to 6.4.12. When editting the pie chart or issue statistics gadget, the filter names are replaced with "filter-12345". Other gadgets I checked still have the filter name from before the upgrade. This is a bit nasty as there is no way for the user to know which filter this is. If you remember, you can search for your filter and hit save, then it is restored. Sounds like a new bug?
//Martijn Wissink

We upgraded or dev environment to 6.4.12 and I can confirm the pie chart and two-dimensional filter statistics are still having problems.

More specifically the two-dimensional gadget when no issues are found it just shows "No Matching Issues Found" however if there are issues, then at the bottom of the table it shows the name of the filter.

The pie chart gadget shows in the title the filter's name if results are returned, but if not, then the title is blank other then "Pie Chart" and in the content area "No Data"

This is really a problem for users, especially for the Pie Chart gadget, because there is no way of knowing what filter is rendering a chart with no data where as with the two-dimensional statistics gadget at the very lest you can click on the link in the "No Matching Issues Found" content area. Gadgets should always show somewhere the underlying filter/project name that provided the data regardless if any issues are returned our not.

JIRA 6.4.12 was already released last week and I have found out that this issue is fixed in my local enviornment: 6.4.12.
You can ddownload 6.4.12 from https://www.atlassian.com/software/jira/download.

@Dieter - I found an option that might help you out. You can have a 2 dimensional filter gadget, and feed it only what you were sorting the pie chart by. It can give you the same information as the pie chart, just without the visual feedback. If your pie chart has many different states, and a lot of options get grouped into "other" the 2 dimensional filter might not be practical, though. I don't know if it does groups like "other".

Sorry to say that but for me this issue is still not fixed. If there is no issue matching the filter the title is still 'Pie chart' only.

There is not a single hint to which filter the gadget is referring

pklimkowski@atlassian.com If only 6.4.12 were released already ...

Hi salvatore.martina1056047739,

Please upgrade to JIRA 6.4.12. If that's not an option you can use the workaround as documented in issue description above.

Hi all,
i have this issue on version JIRA v6.4.11.

any advise?

thanks

Hi all,

The fix will start being rolled out in today's update (Monday 7th of September), so you should receive it in the next few hours.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

Hello:
May we please have a release date for Version 7.0.0-OD-04.
thanks,
Vincent

I agree with Paul: let's not allow one misstep to outweigh an otherwise much larger amount of work well done

We don't we all just take it easy. We should be thankful Atlassian is willing to provide access to its backlog and gaining access to experts and triage folks. Atlassian is hardly incompetent and surely understands the severity of this. I guess I'm just so tired of seeing constant complaints everywhere I step around here. I'm just as aggravated at times, but take a pill and simmer.

@Oswaldo Hernandez [Atlassian] Bugmaster: Can you please confirm why this was reported a week prior to the Cloud update in which it was broken, but it was still rolled out to the Cloud update? This seems pretty incompetent. Are there now measures in place to prevent these critical issues finding their way into Cloud updates when they are already known issues?

...
pushing out this fix in the next JIRA Cloud update
...

So this will be resolved on monday, correct?

no fixVersion == 6.4.x ?

Hi all, the team is currently working on pushing out this fix in the next JIRA Cloud update.

We will update further as it gets deployed.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

Still no feedback and assigned to someone????!!!!
This is a major problem for our business

@Vishwajeet Not just that it made it to the cloud, but it was found before it was released. Dominic far above pointed out that this was reported well before this was applied to OnDemand. Someone thought this wasn't significant and decided to roll it out.

The best work-around I've come up with is to mouse over the links in the chart, and read the URL in the link preview to distinguish the JQL and identify what it's referring to. This might not be good for everyone, but it can be a stop-gap for power users.
My best other guess would be that since the filter gadget is actually working, you can put one with the same filter as the pie chart over the pie chart, limited to display 1 issue. That way it can act as a label in the dashboard. Amazingly ugly, but functional so long as the number of gadgets doesn't wind up going past the limit allowed on a dashboard.

I agree with Vincent. This is a huge issue. Users have master dashboards that are used everyday for reporting. It is impossible to determine what data the pie charts represent.

Atlassian any feedback? seems like a small issue to fix that will make a lot of people happy

Doesn't look like it will fixed soon, as it's still unassigned which mean no one is working on it. That's pretty lame on part of Atlassian that such bug made it to cloud environment and no quick plan to fix it makes it worse.

Oswaldo Hernandez :When is it going to be fixed?

This makes our wall-boards and dashboards useless and needs to be fixed ASAP please.

Priority of this issue should be blocker and what's taking it so long to fix such small bug.

Can you please update on ETA when it will be ready for Cloud version?

It impacts dashboard i create for my customers

Thx

Hi all,

We are aware of the issue and working on deploying a fix to JIRA Cloud as soon as we can.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

This is a pretty severe bug for longstanding, basic functionality. Please fix asap.

I doubt that votes are taken into consideration when planning by Atlassian. If so, we would have features like being able to see the last comment in the issue view. However, increasing numbers can't hurt. More active conversation will likely help, though. Representatives are editing the issue in response to comments here, even if they are needing to be reminded self evident things like OnDemand users can't downgrade. So, I would suggest to keep discussing the details of the impact that this has on your work here.
For instance, I run a daily morning meeting, and I use the pie charts to get a quick aggregate across more than half a dozen searches. After having the titles being invisible to me, I am no longer able to quickly compile this information in order to have a timely morning meeting. Because of that, I can't reasonably maintain enforcement of internal processes the way that I want to. The only work-around I can see for this is to memorize the order of the charts, but that's still an absurd measure to be forced to take.

The listed workaround isn't possible for people on the cloud instance.

Same here, no errors, just the generic title

Ours seems to be the same as yesterday. Still showing "JQL Query" for the title but all the charts are working.

seems to now be worse this morning. I'm now getting error message in some, but not all, of my pie charts

I was told by support that downgrading to jira-gadgets-plugin-6.4.11.jar bundled with JIRA 6.4.9 helps but of course this is no solution for JIRA cloud admins. As a BTF admin i also don't know what might be missing if i use this old version on JIRA 6.4.11 ....

+1 for Bills suggestion

Working with multiple chart on one dashboard is now useless because the title is missing.
People who are reading the dashboards cannot see the difference between the charts because of the title that is missing.
This is a real problem and disturbing the business.

What good is it after a release to have a gadget's title become generic? And on only one gadget, Pie Chart? I agree with Tim Sullivan's approach to resolve the issue. It would provide greater flexibility for the user experience.

Sadly, I do not think votes is the defining factor used by Atlassian to schedule work. Nonetheless, given the workflow for this issue type, it seems it may transition to *Resolved *from here so fingers crossed I suppose, but it is still unassigned.

Everyone - I'm not sure if this will help, but it can't hurt. Please try to get as many people as you can to vote for this issue. There are 36 watchers but only 23 Votes. everyone commenting should be sure to vote and get as many people from your teams as possible to do the same. I would hope Atlassian filters issues so that the ones with most votes rise to top.

This is causing major issues for us since now the charts are meaningless without knowing what they relate to. That said, the proper fix should be to allow a title to be specified for the gadget rather than pulling in the name of the filter. Much better flexibility. You could default to the filter name if left blank. Worked until the cloud update over the weekend.

I think a point not mentioned here that Atlassian should understand is that for a dashboard that, say, I created, others cannot even crack the gadget open for edit to see the filter name behind the pie. Totally useless especially where a dashboard contains several pie charts.

Maybe Atlassian should put a little less money towards their massive advertising campaigns for Service Center and instead hire a few people to respond and fix reported customer issues for existing customers.

Causing more and more trouble every day. We badly need an fix for 6.4.x

Same as other users here, some of my dashboards are only charts and right now they can't be understood.
Dashboards with charts are useless now.

People are asking "what does that represent"? makes Atlassian look bad... please fix as soon as possible

Agree that this is NOT a minor defect and is causing severe impact to us as well since we use lots of pie charts on our dashboards and now e can't tell what each chart does.

Huge problem for us at NBC as well. Like others this only started happening over the weekend. It renders pie charts useless and makes it very difficult to navigate a project. This should be very high priority especially if it is low LOE to repair. Thanks in advance for anything you can do to fasttrack this.

Like others, this is causing disruption and confusion across our projects. Was working fine before the weekend, please fix ASAP.

This essentially renders the dashboard charts useless since you have no idea what is being charted.

I agree with other comments: this was working until this past weekend, and it is extremely disruptive to not know what the source of the data is for a pie chart; in particular when there is more than one of them on a dashboard, as is the case for us

Please figure out how this was broken very recently, and get it fixed with the highest priority

Our projects dashboards messed up due to this problem.
Please fix ASAP.

Also affected - Dashboards with Pie Charts are now meaningless across all users. Can you provide an ETA on a fix, so I can at least inform my users that this is a temporary bug?

This is causing us massive problems across all of our projects! This worked on Cloud on Friday, but was broken over the weekend.

If this was reported 6 days ago (I'm guessing on server version), how was this allowed to make it into a Cloud update?

I don't agree with the priority given (Minor) since the impact is quite severe.
Pie chart is for us the most frequently used gadget, and now it is practically unusable...

Would it be ok to install the jira-gadget-plugin from 6.4.9? At the first glance i didn't note any problems but maybe a developer can confirm this.

This bug is causing many confusion around our customers since now they are faced with multiple pie charts on their dashboard and they don't know which of them displays what ... not acceptable!