If you've been an Atlassian customer for a few years, you might remember when we explained how we take highly-voted issues from jira.atlassian.com into account on our product roadmap: votes are important, but they aren't everything. That hasn't changed. But the way we communicate about feature requests for Jira Server and Data Center, as well as Confluence Server and Data Center, is about to.
Our goal is two-fold:
Customer suggestions for Jira and Confluence Server are coming in by the dozens every day. And that's great! They provide a window into your world that would be hard for us to have otherwise. We read all of the suggestions you send us. Seriously – we do. But we haven't been as good about responding to them.
In some cases, we put a request on the back burner so it can be tackled along with related items on the roadmap. In other cases, the request is quite niche and gets overtaken by requests that would be relevant for a broader set of customers, or isn't in line with the strategic direction of the product. (If that sounds like your request, check out the Atlassian Marketplace for apps that might suit your needs.)
We understand that not getting a response is frustrating. Without an indication of whether your suggestions are being received, and how likely they are to be implemented, it feels like we're not even listening. This is especially true for the highest-voted issues.
Frankly, you deserve better.
In the coming months, you'll see us responding to a lot more of the highly-voted issues in jira.atlassian.com's JSWSERVER, JRASERVER, and CONFSERVER projects. We can't promise you'll always be happy with the answer. But in cases where we decide not to put your suggestion on the roadmap and close out the issue, we can promise a thoughtful, thorough explanation of why.
And let's be honest: we'll never be able to implement all of the suggestions submitted, so you'll notice us close some issues as Won't Fix. But that doesn't mean you're at a dead end. Our ecosystem of Solution Partners can customize your installation in just about any way imaginable, and the Atlassian Marketplace already has add-ons for many user requests that we decided not to address in the base product (e.g., advanced subcomponent support).
We're also designing a new workflow for issues with statuses that make it easier to understand which suggestions we're considering, and where it's at in the process. We'll use this new workflow, along with a regular cadence of ongoing updates, to keep you better informed going forward.
None of this will happen overnight. Please bear with us as we work through the backlog of open issues and implement these process changes internally.
In the meantime, keep those suggestions, votes, and comments coming!
In Jira Server alone, we addressed over 5,000 votes so far this year. This includes some big feature requests such as Kanban backlog, as well as enhancements such as allowing deletion of sprints, drag and drop of subtasks, the ability to see remaining estimate in the workload by assignee summary, and most recently, the #1 voted issue for Jira Server, priorities per project.
As you can see, your participation is vital to our products' development.
Your requests give us amazing insight into what will unleash more of your team's potential. Your votes tell us that small tweaks can make just as much of a difference in your work as splashy new features. And your comments help us get the details right.
I want to extend a huge, heart-felt thank you to everyone who has submitted a suggestion, voted, or commented. We look forward to hearing more of your feedback in the years to come.
Head of Product - Server & Data Center, Atlassian
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events