The gadget defaults to showing the detail view

[Hamilton Colyer-Long]

I do like the fact that you can now click a button to toggle between summary and detail view, this is much nicer than the old gadget that required me to have two gadgets on a lot of our dashboards with one showing the summary and the other showing the detail view. However, because the gadget shows the detail view by default it is very slow to load. On my system I can change the display to show the summary but this is an independent setting per user and I can't do anything to change the view for other people. I think you need to either change the default view to be the summary, or to add a setting that allows the administrator to set the default view. This one may seem a little petty but the slow load times with the new gadget means that some gadgets are ridiculously slow to load when you're loading details of every issue. Some of my dashboards show summaries of work done per project by all our teams, or by all developers in an office, and this is a lot of data when you have 40-50 devs.

[Andriy Zhdanov]

Hi Hamilton,

I think with no details shown it will take the same time to load it. It's just the matter of rendering. You may try it by switching details off and reloading the page. However I agree it's still better to change it to 'No Details' by default for gadgets.

Thank you.

[Hamilton Colyer-Long]

Hi Andriy,

I'm glad you agree that the summary view should be the default, this is definitely the view that our PM's and developers use 90% of the time, and it would be a minor inconvenience to have to change this setting every time you viewed a dashboard.

I'm unable to test the load time in any meaningful way because if you switch details off and refresh the page then it reloads with details turned on again. However, I did find that if I hit the button to show the summary as soon as this becomes available then the summary displays almost immediately, whereas if I wait for the details to load then it takes several seconds. This may be caused by rendering as you suggest, but regardless of the cause it does appear that the summary may display more quickly, which as well as providing more useful functionality to me may also cause less people to comment on performance issues ;)

PS I do want to credit and thank you for your efforts on this component. Whilst I and many other people were pretty disgruntled by the fact that we will now have to pay for a component we thought was part of the core JIRA offering, I do understand that you are running a business and from what I've seen here you're doing a good job at getting the components operating at the levels we expect, responding to feedback, and allowing community involvement - so thank you for that.

Regards, Hamilton Colyer-Long CEO Dapper Apps

[Andriy Zhdanov]

Great, thank you for your kind feedback!

[Andriy Zhdanov]

This should be fixed now

[Hamilton Colyer-Long]

Confirmed fixed.