Browse SpaceMost plugins in the Atlassian Plugin Libraries are free and open source, developed and donated by our community of generous plugin developers. Most of these plugins work well, and provide interesting and useful enhancements to our products.
However, because we didn't write these plugins, Atlassian does not offer support for them. And in the event that they inadvertently cause problems with our software, our support techs may ask you to uninstall them.
We've decided to begin offering support for some of the most widely used and most useful plugins, even ones that weren't created by Atlassian. We've spent some time putting them through their paces and improving the quality of the plugins so that we feel they are reliable. You'll be able to recognize these "certified" plugins by looking for the "Atlassian Supported" icon on their homepage. We're starting with a small list of plugins, but we will be increasing the number of supported plugins over time. Stay tuned for more announcements.
So, if I have a problem or question about a plugin, what should I do?
Supported Plugins
If the plugin you're concerned with has an "Atlassian Supported" icon on its homepage, then please file a ticket in our official support system: http://support.atlassian.com. Please file your ticket against the product you're using. For a problem with a Confluence plugin, use the Confluence Support Project, and so on.
On the other hand, if you find an actual bug with the plugin, you can go straight to the issue tracker listed on the plugin homepage and file a bug there. For most plugins, you can find their JIRA projects on Atlassian's Developer JIRA.
So what does it take for a plugin to be Atlassian Supported? The plugin must:
- be available in Developer Network SVN.
- have its dependencies in the Developer Maven Repository.
- have a JIRA project.
- have a Bamboo Project.
- be in the plugin repository (For Confluence).
- have unit and functional tests with a certain amount of code-coverage.
- have complete, accurate and attractive documentation on Confluence.
- display a compatibility matrix for the last three product releases.
- be internationalized.
Unsupported Plugins
If the plugin in question does not have an "Atlassian Supported" icon on its homepage, please do not file tickets in the Atlassian Support JIRA. We will not be able to answer them. However, you still have a few other avenues to get help.
- Post a question to the Atlassian User forums.
- File a ticket in the plugin's specific JIRA project, listed on its homepage.
- Leave a comment on the plugin's homepage.
These channels are not explicitly monitored by Atlassian staff, but in many cases the plugin's authors or other users will be able to offer help.
Supported Plugins By Label
 | Labels can be edited by any user, so this list may not be 100% accurate. |
Blogging RPC Plugin
(Confluence Extension)
|
|
Chart Plugin
(Confluence Extension)
|
|
Clickr Theme
(Confluence Extension)
|
|
Commit Acceptance Plugin
(JIRA Extensions)
|
|
Confluence Repository Client
(Confluence Extension)
|
|
Contributors Plugin
(Confluence Extension)
|
|
Dynamic Tasklist 2
(Confluence Extension)
|
|
JIRA Calendar Plugin
(JIRA Extensions)
|
|
JIRA Charting Plugin
(JIRA Extensions)
|
|
JIRA Labels Plugin
(JIRA Extensions)
|
|
JIRA Linker Plugin
(JIRA Extensions)
|
|
JIRA Subversion Plugin
(JIRA Extensions)
|
|
Mail Page Plugin
(Confluence Extension)
|
|
Social Bookmarking Plugin
(Confluence Extension)
|
|
TinyMCE Plugin
(Confluence Extension)
|
Hi Gary,
That's exactly our intention here. As you'll note, quite a few of the Supported Plugins, Like ToC and Chart, began as community projects. As far as guidelines go, the ones posted above are the best place to start. If your plugin can meet all those criteria, it will be much more likely that we can offer support for it in the future. That said, the other two things to think about are licensing and usefulness. Be sure you license your plugin with a inclusion-friendly license (we like BSD). Also, we have limited resources, so we're only going to invest our time in plugins that are useful to a broad spectrum of our users.
Cheers,
Jonathan
Posted by Great idea. How do I get a Bamboo build set up for the timecharts plugin?
Would you consider setting up a page where the community can vote for plugins which we'd like to see supported (and perhaps suggest ideas for new ones)?
This might help you direct your efforts by having extra feedback on the more useful plugins (as well as enticing developers of popular plugins to work toward your Supported guidelines).
I would like to suggest a delicious bookmark import plugin 
We started using del.icio.us more than 2 years ago. It now contains well over 2,000 bookmarks that have been collectively tagged by Atlassian employees. Now that Confluence has a social bookmarking feature, we may discontinue using del.icio.us.
It would be cool if there were some way for the Atlassian community to help develop plugins that Atlassian could eventually take on and provide support for, especially for plugins that are widely used.
Is there anything that plugin developers outside of Atlassian can do in the development of their plugins to help make this idea feasible? Obviously, poorly written plugins may not make good candidates for "absorption", and licensing could be an issue, so some plugin writing recommendations might help if this were a possibility.