Summary
- We encourage and display customer comments and votes openly in our issue tracking systems, http://jira.atlassian.com and http://studio.atlassian.com.
- We do not publish roadmaps.
- Product Managers review our most popular voted issues on a regular basis.
- We schedule features based on a variety of factors.
- Our Atlassian Bug Fixing Policy is distinct from our Feature Request process.
- Atlassian provides consistent updates on the top 20 feature/improvement requests (in our issue tracker systems).
How to Track what Features are Being Implemented
When a new feature or improvement is scheduled, the 'fix-for' version will be indicated in the JIRA issue. This happens for the upcoming release only. We maintain roadmaps for more distant releases internally, but because these roadmaps are often pre-empted by changing customer demands, we do not publish them.
How Atlassian Chooses What to Implement
In every major release we aim to implement highly requested features, but it is not the only determining factor. Other factors include:
- Direct feedback from face to face meetings with customers, and through our support and sales channels.
- Availability of staff to implement features.
- Impact of the proposed changes on the application and its underlying architecture.
- How well defined the requested feature is (some issues gain in popularity rapidly, allowing little time to plan their implementation).
- Our long-term strategic vision for the product.
How to Contribute to Feature Development
Influencing Atlassian's release cycle
We encourage our customers to vote on feature requests in JIRA. The current tally of votes is available online in our issue tracking systems, http://jira.atlassian.com and http://studio.atlassian.com. Find out if your improvement request already exists. If it does, please vote for it. If you do not find it, create a new feature or improvement request online.
Extending Atlassian Products
Atlassian products have powerful and flexible extension APIs. If you would like to see a particular feature implemented, it may be possible to develop the feature as a plugin. Documentation regarding the plugin APIs is available. Advice on extending either product may be available on the user mailing-lists, or at Atlassian Answers.
If you require significant customisations, you may wish to get in touch with our partners. They specialise in extending Atlassian products and can do this work for you. If you are interested, please contact us.
4 Comments
Hide/Show CommentsMar 14, 2011
Russ Frizzell
I think another thing to mention in the "influencing Atlassian's Release Cycle" was touched on above it but is worth mentioning again. That is commenting on design ideas for a potential solution.
I know as a software developer that having others put in some design work for you makes the solution easier to implement and better when the comments lead to a healthy discussion among customers of the best way to design a solution rather than the old "I want this really bad, but I'm not sure what the solution would look like."
Again, I know you touched on that in the "well-defined" feature request, but I think it may be worth another mention in the Influencing section.
Your company does an amazing job with communicating with your customers, and your products facilitate that. Thanks again!
Mar 27, 2011
sean diggins
I agree that Atlassian's support is very good. However, the emphasis on voting is fatally flawed and really shouldnt be used as a barometer for customer requests. It skews strongly away from the silent majority (end users in enterprise) towards the vocal minority (small developer shops). This means the squeeky wheel eventually gets the oil, but one vote does not equal one end-user, given most end-users do not interact with Atlassian at all. At the very least, the voting should reflect the license of the voter. Votes from a 2000 user license should be worth considerably more than votes from a 10 user license, but this is not the case with the current system.
Jan 06, 2012
Mark W
I agree with you sean diggins. During my evaluation of JIRA for users in an enterprise environment, I am finding a lot of features and functionality, that I assumed would be basic, left in an unassigned and unresolved state that has been open for 5+ years. It is a little concerning to think that a request for an important feature such as importing and exporting configuration data like workflows can be overlooked by a request to mention other users in comments simply because it had more votes and therefore deemed more wanted by the community.
I love the tools and the support. I just find myself being constantly disappointed in what the tool cannot do in regards to supporting an enterprise.
Jan 23, 2012
Bjørn-Willy Arntzen
I agree with sean diggins and Mark W. It seems to be impossible to get features fixed or added. Wonder how 'big' the company need to be to get things fixed ....