If you’re thinking about entering the Atlassian Codegeist competition, you may already have a plugin in mind that you want to develop. If you don’t, you should consider looking at the ideas on the Plugin Wishlist. The Plugin Library has a complete list of all the plugins that are freely available to customers.
The Plugin Wishlist is exactly that: a list of plugins that we and our customers would like to have. Some of the plugins listed there already exist, but they’re on the list because people would like to see improvements made to them. When you look at the wishlist, some questions may come to mind: who added the item, who reviews the wishlist, and how often do these plugins get built? Here’s a short interview with Jonathan Nolen about the wishlist page:
Who can add a wishlist item?
Anyone can add a wishlist item. The more specific they can be about the plugin, the better. Use cases, screen mockups, and technical implementation ideas will all be tremendously useful when it comes time implement your idea. We tend to add them when someone suggests a feature that we think would be a good idea, and it can be done as a plugin, and we don’t think we’ll get to it ourselves in the near future. We want to encourage people to use the plugin architecture to solve their own problems. After all, there are many more smart people out there in our customer-base than there are inside Atlassian.
Even if you aren’t a programmer yourself, these wishlist pages can serve as a rallying point to get people excited about the feature you want. If you have a great idea, and write up a good spec, don’t be shy about coming to the developer network and trying to recruit other people to your cause.
How often is it reviewed?
We review the list periodically — when we’re planning to outsource plugin development, for example. In the past, we’ve outsourced things like the WebDAV plugin and the Calendar plugin. We’ll continue to pick things off this list and develop them in concert with partners. However, see the answer to the next question.
If something is listed there, when will it be developed?
When you decide to jump in and build it! : ) Seriously, there are already far more ideas on this wishlist than we will ever be able to get to — that’s why we put the wishlist out in public for everyone to see. The idea is that people who might want a particular feature can come together to build it in an open-source fashion. And that people who don’t have programming skills can still contribute by designing a complete feature spec. Knowing what to build is almost as hard as building it.
How are priorities — low, medium, high — determined?
We assign the priorities based on how widely useful we think a given plugin would be. The more people who can benefit from a solution, and the more often they would be able to use it, the higher the priority. But at the same time, there’s no formula — we just set them based on gut feeling. And you should feel free to change them if you have a good reason and can back it up.
Regarding Codegeist, the plugins that we’ve listed as high priority are the ones that we already think would be extremely useful. Submitting a solution to one of those problems would be a smart idea.

Wish upon a Plugin...