As mentioned at the end of last year, we have been working towards improving our feature suggestion process. Our efforts are driven by your need for increased clarity and transparency on feature suggestions.
We're pleased to announce that we now have an updated workflow in place. Each of your suggestions goes through a more structured process that provides greater clarity into where it stands in the context of our product roadmap. We're also using new statuses in the workflow to convey more significant meaning to you.
When you create a feature request, your suggestion automatically enters the Gathering Interest status, and your suggestion stays here until it's generated enough interest. Interest is measured based on several factors, such as the number of votes a request receives, and the UIS (User Impact Score) of the feature. UIS is automatically calculated, taking into consideration factors such as vote velocity and active users impacted. If your request hasn't generated enough interest over time, it will eventually be closed. With the large volume of suggestions that we receive, especially in Confluence and Jira Server, the new criteria will ensure the most popular suggestions are highlighted to be addressed sooner.
Once a request has generated enough interest, it will move into the Reviewing state. In this state, an Atlassian Product Manager will start investigating the viability and relative priority of your suggestion, and then triage it into one of these statuses: Under Consideration, Future Consideration, Not Being Considered.
Under Consideration — Requests that are deemed to bring significant customer value and are likely a strong fit for our roadmap. In this state, there is a high likelihood of delivering the feature in the near future. To keep you in the loop, we will provide an update in the following few months.
Future Consideration — Requests that are deemed a potential addition to our longer-term roadmap. Once a year, we'll reconsider the request and alter the status if needed.
Not Being Considered— Unfortunately, we're unable to implement all of the excellent suggestions you make. When this happens, the requests will take on the not being considered status. While we appreciate the potential benefits of such requests, we won't work on these for the foreseeable future. We'll review such requests after a year, and consider whether we need to alter the status. We understand that it may be disappointing having a suggestion you feel passionately about either be closed or triaged into not being considered. However, we truly believe that we owe you, our customers, greater transparency into the feature requests that you can expect to be implemented, and we believe this new workflow will help us accomplish that for you.
The final resolution of your suggestion may be Resolved: Fixed or Resolved: Won't Do. We may close your feature request as Resolved: Won't Do for a number of different reasons, such as the suggestion has not gained enough customer interest or the suggestion doesn't fit with the direction of our product for the time being. Alternatively, more popular, duplicate suggestions may already exist (we will close the feature request as Resolved: Duplicate) or the suggestion is not expressed clearly enough to be considered thoroughly by a product manager (Resolved: Invalid).
Here's a summary of the new workflow (you can also select View Workflow in the issue status to visualize):
Note: We've implemented the new workflow for Confluence Server, Jira Server, Jira Service Desk Server and Bitbucket Server.
These changes couldn't have been implemented without all of your insights. Also, do keep the feedback wheel turning — this helps us determine how best to improve customer transparency in our processes, how to convey product decisions more clearly, and how to ensure real-time updates on the status of feature requests created.
As always, we look forward to hearing more of your feedback in the years to come!
Head of Product - Server & Data Center, Atlassian
Keshav PuttaswamyAtlassian Team
The wait is over... Portfolio for Jira Server and Data Center 3.0 is now officially here! Platform releases offer Atlassian an opportunity to shift our strategy, make bold predictions about t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs