1.0-m30

Release date: 3rd February, 2014

Removal of email sending resource
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

Required `key` attributes

Confluence dynamic and static macros, as well as JIRA Workflow Post Functions now require an explicit key value.

"dynamicContentMacros": [{
    ...
    "key": "my-dynamic-macro"
    ...
}]

Although not required, we also recommend adding a key attribute to pages and web items.

Confluence macro parameter declarations

In 1.0-m30, dynamic and static parameter macros must also be specified in the URL template for the macro.

Let's take this example of a dynamic macro, which specifies a parameter "city".

"dynamicContentMacros": [{
    "name": { ... },
    "url": "/render-map?pageTitle={page.title}",
    "categories": [ ... ],
    "parameters": [{
        "identifier": "city",
        "name": {
            "value": "Name a city"
        },
        "type": "string"
    }]
}]

Any declared parameters must now also be included in the URL value of the macro in order to serialise this value. For example, your new descriptor should add cityName={city}:

"dynamicContentMacros": [{
    ...
    "url": "/render-map?pageTitle={page.title}&cityName={city}",
    ...
}]

Issues resolved

	Key	Summary
Warning	AC-796	Remove Email sending resource
	AC-839	Wrong text in the Confluence macro browser
Fixed	AC-892	Add-on can store data against a JIRA issue
Fixed	AC-916	JSON descriptor add-ons with OAuth authentication cannot be installed in production instances
Warning	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
	AC-921	iFrame URL parameters with spaces are double-encoded

Deployment Timetable

1.0-m30.1 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.1,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.1,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