Documentation
1.0-m30
Release date: 3rd February, 2014
- Support for JIRA issue properties
- Make AP.messages API stable
- Whitelisted remote endpoints are listed in the documentation
- Fix bug with OAuth and JSON descriptor
- AC Play support for JSON descriptor and JWT. Read the upgrade guide
Issues resolved
| Key | Summary | |
|---|---|---|
| AC-839 | Wrong text in the Confluence macro browser | |
| AC-892 | Add-on can store data against a JIRA issue | |
| AC-916 | JSON descriptor add-ons with OAuth authentication cannot be installed in production instances | |
| AC-917 | Make AP.messages API stable (nb: breaking changes) | |
| AC-918 | As a Connect add-on developer, I'd like to browse through the available REST APIs I have access to from within the Connect documentation |
Deployment Timetable
1.0-m30 is scheduled for deployment on 10th February 2014.
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-m30,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-m30,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