Hi everyone,

Thank you for your interest in this issue.

While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. The change requires an architecture change that may negatively affect other product areas, especially performance.

After careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, some of them including your highly voted suggestions:

• Further performance and stability improvements
• Adding the "updated-by" JQL search query JRASERVER-1973
• Support for 4 byte characters in MySQL connection JRASERVER-36135
• Jira email notifications batching JRASERVER-1369
• Mobile app for Jira Server JRASERVER-46149
• Email notifications template editor available from the UI JRASERVER-7266
• Improved filter and dashboard management by Jira administrators JRASERVER-15900 and JRASERVER-41269

In the recent Jira Server releases we have shipped some highly-voted features and improvements, including:

• Filters and dashboards collaborative editing
• Selectable delimiters in CSV export 
• Microsoft SQL Server 2016 support 
• iPv6 support
• Faster Kanban boards
• Refreshed projects and custom fields management pages in the admin's section 

We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

To learn more on how you suggestions are reviewed, see our updated workflow for server feature suggestions.

Kind regards,
Jira Server Product Management