JIRA team, guys, it's not serious. You've removed most useful gadgets from the product. I have no idea how can I work without an agile classical gadget. It seems like I have to concider non-JIRA options.

As well as doing burndown per sprint, we need to be able to do burndown per epic or feature. This was previously possible but not after upgrading to the newest JIRA, please give back this functionality.

Please replace the Agile classic gadget. Our teams have made heavy use of these and are refusing to upgrade because they don't want to loose this board. I agree with the above comment, never remove functionality.

There used to be a way to get the "Days until" gadget for a Fix Version (e.g. for a release, not just an individual sprint), but now with the removal of the classic gadgets there is no way to get this number on JIRA dashboards, which is disappointing as it is a useful thing to be able to display.

As mentioned in an earlier comment, it's also a shame that Atlassian are removing existing functionality without providing viable alternatives as standard.

Agree with the above comments. Some of our development teams which used the Agile Classic Gadget are now having a tough time trying to find replacement gadget with similar functionality.
Any inputs on alternate/replacement gadget with similar functionality would be great!

I have been using this gadget as well, specifically the hours tab. It provides much more detail (daily hours, estimate accuracy, required daily burndown rate, etc.) than the Sprint Burndown Gadget. I agree with all other respondents - please leave these gadgets in the product until an equivalent is available within JIRA. I really do not want to have to go to the marketplace in order to pay extra for something I already have - like the print card option.

I have been using the Agile Classic gadget to roll up a view of work across multiple Scrum teams. I am unable to find anything comparable among the new gadgets, which all seem to be geared to a single Scrum team. I agree with Daniel that the Agile Classic gadgets should remain in the release when there is not an equivalent available.

We use Agile Classic Gadget as our the most important gadget on dashboard. Right now there is no way to track time estimates in sprint as old gadget was removed. Could you leave old gadgets for the time, when no equivalents are available? As Tatu Kuusimurto wrote - we have very limited options available now.

In my opinion the priority of this issue is completely off. It should have at least the priority of major.
The reason is that we have unfortunately built our automatic status reporting mechanisms on top of the classic agile gadget by creating status wiki pages into our Confluence wiki, that show different metrics on the ongoing projects on release and epic-level. (we're mainly using burnup, flow and velocity graphs)

Now when the Agile Classic gadget ceases to exist there are only a few options for us:

• Stop updating Jira and Jira Agile (not good, since we'd be missing all the nice improvements with the tool and would get no support with issues)
• Stop using the agile gadget and report by other means. (No other automatic options available, manually reporting is not feasible as we have multiple projects and metrics that the management is used to follow.)
• Move to another backlog handling tool and or wiki. (quite a large work to move everything, but doable. Maybe reporting manually would still be the smaller pain though)

So to be frank, none of the above are very tempting, which means we REALLY need an alternative for the Agile Classic gadget!