1.0-m31

Release date: 10th February, 2014

Support for Inline Dialogs
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".
Improvements to "Error contacting remote application host" error handling

Add-on `version` attribute

The version attribute of the module descriptor should no longer be used. Instead, the apiVersion attribute is now preferred and provides a mechanism to test beta versions of your add-on. The version attribute is now ignored and the Atlassian Marketplace will create an internal version for it's use. Also see: upgrades and versioning.

Issues resolved

	Key	Summary
Fixed	AC-206	As a developer, I can create an inline dialog from a web-item location
Fixed	AC-926	AP.request is broken inside inline-dialog iframes
	AC-928	Add missing `myself` JIRA REST APIs to scopes
	AC-924	Web items should use fully qualified complete key for linkId
	AC-934	Failing to specify a scope should not result in "Error contacting remote application host" error message during plugin installation
	AC-933	JSON descriptors fail on upgrade whilst looking up SEN
	AC-906	Uninstall plugin error

Deployment Timetable

1.0-m31 is scheduled for deployment on 17th February 2014.

Testing

You can start JIRA or Confluence with Atlassian Connect as follows:

JIRA

atlas-run-standalone --product jira --version 6.2-OD-09-036 --bundled-plugins com.atlassian.plugins:atlassian-connect-plugin:1.0-m31,com.atlassian.jwt:jwt-plugin:1.0-m8,com.atlassian.bundles:json-schema-validator-atlassian-bundle:1.0-m0 --jvmargs -Datlassian.upm.on.demand=true

Confluence

atlas-run-standalone --product confluence --version 5.4-OD-5 --bundled-plugins com.atlassian.plugins:atlassian-connect-plugin:1.0-m31,com.atlassian.jwt:jwt-plugin:1.0-m8,com.atlassian.bundles:json-schema-validator-atlassian-bundle:1.0-m0 --jvmargs -Datlassian.upm.on.demand=true