Documentation
1.0.0-rc2
Release date: 19th February, 2014
- Fixed connect plugin and connect addon lifecycles
- Installing an add-on into OnDemand will not work unless the base url starts with https
- Support for context parameters on remote conditions
- Only add-ons with a
baseUrlstarting withhttps://can be installed in OnDemand servers.http://may still be used for testing locally.
Breaking Changes
- 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
- The
authenticationmodule is now required - WebPanel url and location fields are now required
Issues resolved
| Key | Summary | |
|---|---|---|
| AC-966 | Add /rest/api/2/groups/picker to JIRA scopes white-list | |
| AC-965 | WebPanel url and location should be required fields | AC-451 | Remove xdm_p parameter |
| AC-962 | /download/attachments/ not part of the confluence READ scope | |
| AC-912 | Validate that Connect baseurl uses https protocol in production | |
| AC-944 | Add issueLinkType mutators to JIRA scopes | |
| AC-942 | Macro editor dialog buttons are not functional | |
| AC-948 | license parameter (lic) not passed to jiraSearchRequestViews requests | |
| AC-868 | user_key not provided in remote-search-request-view request, fails OAUTH | |
| AC-934 | Failing to specify a scope should not result in "Error contacting remote application host" error message during plugin installation | |
| AC-817 | Add additional parameters to remote conditions | |
| AC-956 | json descriptor admin pages do not auto-resize | |
| AC-904 | Webitem urls are missing standard context variables | |
| AC-905 | New Confluence REST api should be accessible to Connect add-ons | |
| AC-937 | Make "authentication" module required | |
| AC-853 | Add Variable Substitution for Absolute URLs | |
| AC-964 | When dialog opened through AP.require('dialog') background does not get dimmed | |
| AC-952 | Multiple of the same connect macro on one page don't render correctly |
Deployment Timetable
Testing
You can start JIRA or Confluence with Atlassian Connect as follows:
JIRA
atlas-run-standalone --product jira --version 6.2-OD-08-034 --bundled-plugins com.atlassian.plugins:atlassian-connect-plugin:1.0.0-rc2,com.atlassian.jwt:jwt-plugin:1.0-m8,com.atlassian.bundles:json-schema-validator-atlassian-bundle:1.0-m0,com.atlassian.upm:atlassian-universal-plugin-manager-plugin:2.15 --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.0-rc2,com.atlassian.jwt:jwt-plugin:1.0-m8,com.atlassian.bundles:json-schema-validator-atlassian-bundle:1.0-m0,com.atlassian.upm:atlassian-universal-plugin-manager-plugin:2.15 --jvmargs -Datlassian.upm.on.demand=true