This page last changed on Nov 22, 2009 by smaddox.

20 November 2009

With pleasure, Atlassian presents Atlassian Gadgets 2.0.

This release of Atlassian Gadgets contains the features and improvements that will allow Confluence to display and publish gadgets. With the upcoming Confluence 3.1 release, you will be able to add gadgets to a wiki page. Confluence will also publish gadgets, so that you can include Confluence gadgets in JIRA or on a Confluence page.

The Atlassian Gadgets JavaScript Framework is now part of Atlassian Gadgets. Before this release, the JavaScript framework was available only to gadget developers in JIRA 4.0. With Gadgets 2.0, gadget developers can use the JavaScript framework in the upcoming release of Confluence 3.1 and future releases of all Atlassian applications.

Atlassian Gadgets 2.0 introduces gadget subscriptions. Note: This feature is not yet available in any Atlassian applications. When implemented in the applications, this feature will allow administrators to make all the gadgets from one application available in another application. For example, let's say you have a JIRA site that publishes some gadgets and a Confluence site that can display gadgets. The Confluence administrator would not need to add each gadget individually. Instead, your Confluence site could subscribe to JIRA's gadgets, making all your JIRA gadgets immediately available for inclusion on Confluence pages.

Highlights of this Release:

Want to develop an Atlassian gadget?
Take a look at the gadget developer guide. Then see how to use the Atlassian Plugin SDK and wrap your gadget as a plugin.

Comments, Requests and Feedback
We would love your feedback. Please log your requests, bug reports and comments in our issue tracker.

Highlights of this Release

Gadgets in Confluence 3.1

This release of Atlassian Gadgets contains the features and improvements that will allow Confluence to display and publish gadgets. The following features are planned for the upcoming Confluence 3.1 release:

  • Confluence will publish gadgets, so that you can include Confluence gadgets in JIRA or on a Confluence page.
  • You will be able to add gadgets to a wiki page. This means that you can embed a gadget within the text as part of the page content, or build a dashboard-like wiki page displaying a number of gadgets. The gadgets can display data from your Confluence, JIRA or Bamboo site. You can even display content from somewhere else entirely, for example by adding a Google gadget to a Confluence page.

JavaScript Framework

Atlassian Gadgets now incorporates the Atlassian Gadgets JavaScript Framework. Before this release, the JavaScript framework was available only to gadget developers in JIRA 4.0. With Gadgets 2.0, gadget developers can now use the JavaScript framework in the upcoming release of Confluence 3.1 and future releases of all Atlassian applications. See the sample OAuth gadget for a simple example of how to use the JavaScript framework.

Gadget Subscription

Atlassian Gadgets 2.0 introduces gadget subscription. This feature allows administrators to include all the gadgets published by one application into the directory of another application. We call this 'subscribing' to the application's gadgets.

Please note: Although this feature is now part of the framework, it has not yet been included into any Atlassian applications. We plan to make it available in future releases of Confluence, JIRA and others.

To make use of this feature, you will need two or more applications that support the feature. For example, if you have a JIRA site that makes some gadgets available and a Confluence site that can display gadgets, then your Confluence site can subscribe to your JIRA gadgets. There is no need for the Confluence administrator to enable each JIRA gadget individually. The JIRA gadgets will show up in the Confluence macro browser, and Confluence users will be able to add the JIRA gadgets to their wiki pages.

Other Things Worth Mentioning

This release brings number of bug fixes and improvements. The full list is below. The following deserve a specific mention:

  • The Atlassian Gadgets framework now provides enhanced support for the OpenSocial data model. The framework can handle requests for information about people, groups, activities and data. It also supports the creation of an activity. Note that, although this feature is now part of the framework, it has not yet been included into any Atlassian applications. This means that gadget developers cannot yet make use of the feature, but it is available for building into future application releases.
  • Gadgets added to a dashboard from the directory will now reflect the proper locale immediately. Previously, you had to reload the dashboard to see the change.
  • The framework now issues improved error messages when there is a problem with loading a gadget.
  • We have introduced JavaScript unit tests, as well as numerous improvements to integration tests and Selenium tests.
  • There is additional JavaScript console logging when you run with minification disabled. We recommend that you turn off both batching and minification during gadget development, but turn them on during testing.
  • When making HTTP requests, the Atlassian Gadgets framework now uses the JVM proxy configuration.

Complete List of Fixes in this Release

JIRA Issues (123 issues)
Key Summary Priority Status
AG-1176 Build failure on GadgetSpecFeedResourceTest Blocker Resolved
AG-1159 Gadget resizing is broken with embedded gadgets Blocker Resolved
AG-647 Split persistent gadget ID from Shindig module ID Critical Resolved
AG-1158 Look at ActivityService compliance tests Major Resolved
AG-1157 PPL802 : Handling for out-of-bounds person requests Major Resolved
AG-1156 APP009 : update request with key "*" and empty values should delete all fields Major Resolved
AG-1155 PersonId validation Major Resolved
AG-1154 AppData should use app-specific namespace Major Resolved
AG-1153 Update base POM to version 22 Major Resolved
AG-1149 Use better matchers in test code Major Resolved
AG-1135 LocalGadgetSpecFactory should always log at the WARN level Major Resolved
AG-1130 Opensocial compliance tests Major Resolved
AG-1114 Tests for relative url for appId in ShindigActivityServiceImpl and ShindigAppDataServiceImpl Major Resolved
AG-1113 Please update the version number in the help-paths.properties file Major Resolved
AG-1100 Implement ShindigActivityServiceImpl.getActivities and deleteActivities Major Resolved
AG-1097 PluginSettingsAppDataService should treat empty set of fields as "all fields" Major Resolved
AG-1093 Unit tests for AppDataService Major Resolved
AG-1092 Examine SecurityToken wrapper Major Resolved
AG-1090 Concurrency audit of PluginSettingsActivityService and PluginSettingsAppDataService Major Resolved
AG-1089 Reevaluate our Activity class Major Resolved
AG-1087 Fixed set of Person attributes across apps? Major Resolved
AG-1086 Better signature for AppDataService.updatePersonData Major Resolved
AG-1084 specUrl/appId passed into service methods should be relative? Major Resolved
AG-1083 Change spring/guice binding of opensocial services Major Resolved
AG-1082 Fields parameter in ActivityService implementation Major Resolved
AG-1081 ActivityService.createActivity should return Activity Major Resolved
AG-1080 changes to IncorrectStoredDataException Major Resolved
AG-1079 use domain classes to represent IDs Major Resolved
AG-1078 ActivityService.createActivity should take an Activity, not an Activity.Builder Major Resolved
AG-1077 small review changes for person service Major Resolved
AG-1076 small review changes for appdata service Major Resolved
AG-1075 small review changes for activity service Major Resolved
AG-1073 Gadget syndication feed throws NPE Major Resolved
AG-1071 Transaction handling for OpenSocial Major Resolved
AG-1069 Chance @since tags from 1.1 to 2.0 Major Resolved
AG-1068 Change the 1.1.0 version in JIRA to 2.0.0 Major Resolved
AG-1067 Change the version number in the POMs from 1.1.0-SNAPSHOT to 2.0.0-SNAPSHOT Major Resolved
AG-1066 Change version 1.1 to 2.0 Major Resolved
AG-1063 Checkbox doesn't save anything to user preferences Major Resolved
AG-1062 Multi-select field only stores the last selected option Major Resolved
AG-1059 HttpClientFetcher doesn't follow redirects Major Resolved
AG-1057 Publish DirectoryImpl service via OSGi Major Resolved
AG-1055 Mavenize template generation Major Resolved
AG-1052 downcast in shindig Major Resolved
AG-1051 Handle legacy SPI Major Resolved
AG-1048 make gadgets transparently remember and default to their last vertical size Major Resolved
AG-1047 Simulate other browser behavior like cookies, so we could create better JS unit tests Major Resolved
AG-1046 Add package-info.java files to spi subpackages Major Resolved
AG-1042 Add gadget-common-fields.js to com.atlassian.gadgets.publisher:ajs-gadgets resources? Major Resolved
AG-1040 Eliminate unnecessary dependencies in opensocial-plugin Major Resolved
AG-1039 Opening dropdowns in a readonly dashboard causes a javascript error Major Resolved
AG-1038 Update RefApp dependency to 2.3.14 Major Resolved
AG-1037 Update OAuth dependency to the 1.0 final release Major Resolved
AG-1036 Update ATR dependency to 1.0 final release Major Resolved
AG-1035 Update Atlassian Plugins to the final 2.3.0 release Major Resolved
AG-1034 Update Atlassian Hamcrest to the final 1.0 release Major Resolved
AG-1033 Remove logging.properties from renderer plugin Major Resolved
AG-1031 HttpClientFetcher is caching all responses (including ones with no cache directives) Major Resolved
AG-1028 GadgetIframeTester should give a better error message when elements are not found Major Resolved
AG-1026 AG.params that should be null take on previous param's value Major Resolved
AG-1025 Add support back in for the #oauth callback URL Major Resolved
AG-1023 Include CSS from JIRA Major Resolved
AG-1022 Remove old ajs-gadgets.js Major Resolved
AG-1020 Mavenize JS debug code stripping Major Resolved
AG-1019 Use individual ajs-gadgets JS files rather than the concatenated version Major Resolved
AG-1018 Mavenize JS minification Major Resolved
AG-1017 move parser classes and their tests into refapp Major Resolved
AG-1015 Update OAuth, ATR and RefApp deps Major Resolved
AG-1014 Un-hose dependency injection for shindig's JsonContainerConf Major Resolved
AG-1013 Rename renderer plugin to opensocial plugin Major Resolved
AG-1012 Implement AppDataService Major Resolved
AG-1009 Improve logging of SSL exceptions in HttpClientFetcher Major Resolved
AG-1008 Directory should not be in an internal package Major Resolved
AG-1006 Write Selenium tests for Dashboard Tabs Major Resolved
AG-1004 Reduce log level to DEBUG for log message Major Resolved
AG-1002 Integrate gadgets.js from JIRA into AG publisher plugin Major Resolved
AG-1001 refactor GadgetUserPrefsTest Major Resolved
AG-1000 move DashboardParserTest to Test Framework sub module Major Resolved
AG-998 Update translations for German, French (maybe Japanese) when available Major Resolved
AG-996 Cannot restore from Canvas mode once the gadget is minimised Major Resolved
AG-993 Upgrade to refapp 2.3.9 Major Resolved
AG-991 When a gadget cant be found it does not give enough information to find out why Major Resolved
AG-990 Re-enable social-api module in shindig vendor branch Major Resolved
AG-989 Add some report logging to the javascript tests (surefire-reports or something similar) Major Resolved
AG-988 Implement ActivityService (org.apache.shindig.social.spi.ActivityService) Major Resolved
AG-987 Implement PersonService (org.apache.shindig.social.spi.PersonService) Major Resolved
AG-986 Add opensocial support to the renderer plugin Major Resolved
AG-984 Seperate the directory plugin from dashboards Major Resolved
AG-983 Fix Columns Tests Major Resolved
AG-982 Finalize implemetation of Gadget Drag and Drop test Major Resolved
AG-981 Test Gadget Directory Categories Major Resolved
AG-977 Ensure that all dependencies are available in the public maven repository Major Resolved
AG-975 Register alternate consumer name when creating token properties Major Resolved
AG-973 Get JSUnit tests running as part of the build with appropriate notifications Major Resolved
AG-972 Write Javascript tests for 4 recent bugs Major Resolved
AG-971 Javascript Tests Major Resolved
AG-970 Display gadgets from more than one directory in the Directory Major Resolved
AG-969 Allow admininstrator to define list of other directories to subscribe to Major Resolved
AG-968 Retrieve list of all gadgets published by a container Major Resolved
AG-967 OpenSocial Person + Activity API/SPI Major Resolved
AG-964 I18n Test gadget sometimes shows incorrect expected text Major Resolved
AG-934 Cursor changes to "move" icon on gadget header hover in read only dashboards Major Resolved
AG-922 Viewing the gadget preference in canvas mode hides part of the gadget Major Resolved
AG-882 Tab text and title attribute are being double html escaped Major Resolved
AG-744 Selenium tests should not use external gadgets Major Resolved
AG-666 Caching of OAuth responses Major Resolved
AG-491 Gadget added from directory is not obeying the locale of dashboard Major Resolved
AG-482 Write instructions on writing & running Selenium tests Major Resolved
AG-480 Ensure there is a Selenium build that send notifications to committers Major Resolved
AG-479 Selenium tests fail trying to add the TreeFrog Gadget Major Resolved
AG-420 The drag option for gadgets should be disabled when they are in maximized state Major Resolved
AG-1167 Searching for some gadgets in gadget directory doesn't reset it when user access the directory next time Minor Resolved
AG-1132 Put focus in search box when bringing up the directory dialog Minor Resolved
AG-1118 don't create PersonId, ActivityId, or AppId with null id Minor Resolved
AG-1049 ui-tests module suggestions Minor Resolved
AG-995 Refactor test-framework Minor Resolved
AG-992 Improve wording on the 'no ALLOW' error message Minor Resolved
AG-979 Remove dependence on external tests Minor Resolved
AG-950 Add external gadget textbox has different behavior(gadget error, not proper/ supported) when user try to add gadget by clicking enter/clicking "Add button" Minor Resolved
AG-931 After adding a gadget, exisitng gadget fields overlay the gadget browser on IE6 Minor Resolved
AG-888 IE6: Operations Tools item has no hoverstate Minor Resolved
AG-683 Gadgets in directory are getting displayed in single column for some categories in firefox 3 on windows Minor Resolved
AG-909 The alignment of menu icons for gadgets having canvas mode in not straight Trivial Resolved


Document generated by Confluence on Nov 22, 2009 17:46