Most plugins in the Atlassian Plugin Libraries are free and open source, developed and donated by our community of generous plugin developers. Some other plugins in these libraries were written by Atlassian developers to serve some specific purpose (or because the developer wanted to try something new) but have not yet been brought up to the quality standards we'd prefer. Most of these plugins work well, and provide interesting and useful enhancements to our products.
However, because we have not yet been able to ensure these plugins meet the quality standards outlined below, 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 Atlassian Plugin Exchange.
- 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.
We endeavor to help non-Atlassian plugin authors keep their plugins up to date and working in each new Atlassian release. We provide betas of our products during the development cycle though our Early Access Programs. We provide development-milestone binaries in our Atlassian Maven Repositories to faciliate testing with new versions of the software. We provide release and upgrade notes which explain changes affecting plugin development. We provide our source-code and API documentation. And finally try to respond to development queries in the Developer Forums to help people upgrade their plugins for new releases.
That said, unsupported plugins are the responsibility of their authors or the user-community: not Atlassian. We cannot test or upgrade all of the plugins that have been contributed.
Supported Plugins By Label
JIRA
FishEye for JIRA
(JIRA Extensions)
|
|
JIRA Subversion Plugin
(JIRA Extensions)
|
|
JIRA Perforce Plugin (Discontinued)
(JIRA Extensions)
|
|
JIRA Bamboo Plugin
(JIRA Extensions)
|
|
JIRA Charting Plugin
(JIRA Extensions)
|
|
JIRA Calendar Plugin
(JIRA Extensions)
|
|
JIRA Commit Acceptance Plugin
(JIRA Extensions)
|
|
JIRA Linker Plugin
(JIRA Extensions)
|
|
JIRA Labels Plugin
(JIRA Extensions)
|
Comments (11)
Nov 12, 2007
Gary S. Weaver says:
It would be cool if there were some way for the Atlassian community to help deve...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.
Nov 14, 2007
Jonathan Nolen says:
Hi Gary, That's exactly our intention here. As you'll note, quite a few of the ...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
Nov 12, 2007
Bob Swift says:
Jonathan, excellent! And I see the link to Bamboo for monitoring builds.Jonathan, excellent! And I see the link to Bamboo for monitoring builds.
Nov 13, 2007
Matt Doar says:
Great idea. How do I get a Bamboo build set up for the timecharts plugin?Great idea. How do I get a Bamboo build set up for the timecharts plugin?
Nov 14, 2007
Jonathan Nolen says:
If you want a Bamboo Build for your project, email me directly. I don't have a p...If you want a Bamboo Build for your project, email me directly. I don't have a process sorted out for this yet, but I'm working on it.
Cheers,
Jonathan
Dec 20, 2007
Chris Walker says:
Would you consider setting up a page where the community can vote for plugins wh...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
Jul 08, 2008
Paul Csapo says:
Dear Atlassian, please can you reply back with an official page of Plugins that ...Dear Atlassian, please can you reply back with an official page of Plugins that you support.
If a page already exists, please can you let me know as I may have missed it.
many thanks,
Paul
Jul 08, 2008
Jonathan Nolen says:
This is the official list, and also any supported plugin will have the supported...This is the official list, and also any supported plugin will have the supported icon on its homepage.
Dec 22, 2008
Tyler Theobald says:
Do I have to go to each plugin and see if it has a "supported" pic? I'd li...Do I have to go to each plugin and see if it has a "supported" pic? I'd like to only consider supported plug-ins for our production instance of JIRA and would like to get a list of ONLY supported plug-ins.
Thanks.
Jan 12, 2009
Jeremy Largman [Atlassian] says:
The content by label macro was looking in the wrong space. I've fixed it now so ...The content by label macro was looking in the wrong space. I've fixed it now so the supported plugins are showing.
Mar 18, 2009
Paul Chen says:
The SQL Plugin would be very useful at my company, but our Confluence Administra...The SQL Plugin would be very useful at my company, but our Confluence Administrators are reluctant to add an Unsupported plugin. Where can I find more information on how I can help insure all the Atlassian supported plugin criteria are met - Reference "what does it take for a plugin to be Atlassian Supported?" above?
For example, how do I get a plugin project in the "Developer Network SVN", get a new Bamboo project, or what is the minimum code coverage required? A little more detail on next steps would be helpful.
I'll investigate each bullet more and work on my business case with IT