Documentation

Release Notes

1.0.1

  • Allow POST method for "screens/addToDefault/{fieldId}"
  • UPM auto-update fails to upgrade add-on

1.0.0

  • Installing an add-on into OnDemand will not work unless the base url starts with https
  • Support for context parameters on remote conditions
  • The add-on key must now be less than or equal to 80 characters. Any add-ons with larger keys will need to be shortened
  • Module key attributes are now required
  • WebPanel url and location fields are now required
  • Only add-ons with a baseUrl starting with https:// can be installed in OnDemand servers. http:// may still be used for testing locally.
  • Increased security: add-ons are assigned a user in each product instance in which they are installed and server-to-server requests go through authorisation checks as this user.
  • Fixes issue where user_is_logged_in condition caused general pages to not be viewable
  • Fixes numerous issues with context parameters not being sent through to conditions and pages
  • Removes page header from Confluence general pages

1.0-m31

  • Support for Inline Dialogs
  • The authentication module is now required
  • Add-ons that request JWT authentication will now fail to install if they do not specify an "installed" lifecycle callback. To opt out of JWT authentication, you may specify an authentication type of "none".

1.0-m30

Read the 1.0-m30 release notes.

1.0-m29

  • Tabs can now be added to Confluence Space Tools section. Check out Space Tools Tab documentation for more information
  • Support for web sections
  • Support for full screen dialogs
  • AC Play support for JSON descriptor and JWT. Read the upgrade guide

Read the 1.0-m29 release notes.

1.0-m28

  • New documentation for the Atlassian Connect Javascript API
  • Java 7 is no longer required at runtime (change in atlassian-jwt 1.0-m8)
  • JSON descriptors that request web-hooks must now also request the corresponding scopes required to receive these web-hooks
    • Without the correct scope you will see an error in the host product's log during installation that tells you which scope to add
  • JIRA REST API endpoints are in the JSON descriptor scopes white-list
    • If your add-on uses these endpoints then you can now specify scopes in your descriptor and they will be respected in authorisation checks on requests to JIRA
    • E.g. add "scopes": ["READ", "WRITE"] to your JSON descriptor if your add-on performs read-only actions and mutating actions
    • Scopes white-list documentation coming soon so that you will be able to figure out which scope is required for each endpoint that you access

Read the 1.0-m28 release notes.

1.0-m27

  • Support for Macro image placeholder values
  • Support for long query parameters for remote macros
  • web-item module link attribute renamed to url
  • Fixed bug which prevented incoming JWT requests from being accepted
  • Fixed the configure page url with JSON descriptor
  • Better error reporting and bug fixes for JSON descriptor
  • Docs are now available in product. Just visit https://HOSTNAME:PORT/CONTEXT_PATH/atlassian-connect/docs/

Additionally, we have relaxed the deprecation period for the XML descriptor until 28th February, 2014.

Read the 1.0-m27 release notes.

1.0-m25

Atlassian Connect 1.0-m25 introduces a number of changes to how you will build add-ons for Atlassian OnDemand. There are two important changes in this release: a new format for your add-on descriptor and a new authentication method. Both of these changes are designed to help developers build add-ons more quickly and easily.

  • JSON Add-on Descriptor
  • JSON Web Token (JWT) Authentication
  • atlassian-connect-express v0.9.0

These new features replace the XML descriptor and OAuth, which are now deprecated. Please read the deprecation notices.

Read the 1.0-m25 release notes.

Earlier Releases

For earlier release notes, please see the Atlassian Connect Blog.