Hi everyone,

Thanks for providing your thoughts and votes on this suggestion. We know it's been a while since this suggestion was raised and we're sorry to have kept you so long without a clear answer.

As you probably know, the removal of support for these gadgets was the result of replacing the Classic boards that existed prior with Agile boards starting with Jira 7.0. When Agile boards were built, we considered the cost of rebuilding gadgets in the new design and the impact on other areas of the product. At the time, the decision was made to release Agile boards without this capability.
You can read more about the introduction of the Agile boards and deprecation of the Classic boards in the original communication here.

As the Jira server team, we have recently reviewed this suggestion in the context of our current strategy and priorities. We understand your need for gadgets like we had with Classic boards. However, we wanted to share that this is not a capability that we plan to address in the next 12 months.

Your feedback has told us that there are other areas we need to solve first as they are more pressing and have a bigger impact to you. These include:

• Solving problems with Mail Server and handling mail queue issues
• Reducing the amount of email notifications being generated by Jira
• Improved Jira UI
• Allowing users to edit shared filters and dashboards

We do believe this is a valid request and would like to revisit in the future to see if it can make it on our roadmap.

I understand that our decision may be disappointing but we also hope that you will appreciate our candid and transparent approach. Please don't hesitate to contact us if you have any questions.

Thanks,
Jakub Lazinski
Product Manager, Jira Server

How does Atlassian deprecate a feature actively used by most customers without offering any alternate solution? Not having an official response from Atlassian, having this marked as a 'Suggestion' when really it is a feature deprecation, seeing the ticket still unassigned – all read as Atlassian not paying attention to their customers.

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.