Documentation

Release Notes

1.2.42

1.2.41

1.2.38

1.2.37

1.2.36

1.2.35

1.2.34

1.2.32

1.2.31

1.2.28

1.2.26

1.2.25

1.2.23

1.2.22

1.2.19

1.2.15

New JIRA user role condition

In order to solve AC-2067 we have added a new entity_property_contains_any_user_role condition. This is very similar to the entity_property_contains_any_user_group condition. It is aliased by the addon_property_contains_any_user_role condition, for which the entity parameter is omitted.

This condition allows you to check whether or not the browser user has any role specified in that entity property, which must be an array of strings. For example, you may have an issue entity property called myConfig containing the following value:

{
    "myListOfRoles": [ "developers", "support-staff" ]
}

Then you could write the following condition to restrict the display of a module to a user with at least one of those roles:

{
    "condition": "entity_property_contains_any_user_role",
    "params": {
        "entity": "issue",
        "propertyKey": "myConfig",
        "objectName": "myListOfRoles"
    }
}

1.2.10

New JIRA & Confluence user group membership conditions

In order to solve AC-804 we have added a new entity_property_contains_any_user_group condition. This condition has the following aliases:

  • addon_property_contains_any_user_group
  • content_property_contains_any_user_group
  • space_property_contains_any_user_group

This condition allows you to check whether or not the browser user is a member of any group specified in that entity property, which must be an array of strings. For example, you may have an issue entity property called myConfig containing the following value:

{
    "myListOfGroups": [ "developers", "support-staff" ]
}

Then you could write the following condition to restrict the display of a module only to a user in at least one of those groups:

{
    "condition": "entity_property_contains_any_user_group",
    "params": {
        "entity": "issue",
        "propertyKey": "myConfig",
        "objectName": "myListOfGroups"
    }
}

1.2.9

New Confluence context parameters

Confluence now supports the additional context parameters related to attachments:

  • attachment.id
  • attachment.name
  • attachment.mediaType

1.2.8

New has_attachment JIRA Condition

The has_attachment condition can be used to check whether the currently displayed issue has any attachments. Additionally, an optional extension param may be provided to check if it has an attachment with a specified file extension (case insensitive).

For example, to check if the issue has any PDF files attached, the condition should be specified thus:

{
  "condition": "has_attachment",
  "params": { 
    "extension": "pdf"
  }
}

New entity_property_exists JIRA and Confluence Conditions

In order to solve AC-2169 we have added a new entity_property_exists condition. This condition has the following aliases:

  • addon_property_exists
  • content_property_exists
  • space_property_exists

This property allows you to check for the existence of an entire entity property or a single field within that entity property. For example, if you have an issue entity property called extraUrls and it has the following value:

{
    "standardUrls": [
        "http://path.to.somewhere.com",
        "http://path.to.somewhere.else.com"
    ],
    "sidebarUrls": [
        "https://www.atlassian.com",
        "https://marketplace.atlassian.com"
    ]
}

Then you could write a condition in your descriptor that could check if the sidebarUrls property exists on a given issue. That condition would look like this:

{
    "condition": "entity_property_exists",
    "params": {
        "entity": "issue",
        "propertyKey": "extraUrls",
        "objectName": "sidebarUrls"
    }
}

You can use this new condition to write powerful new functionality for your add-on.

AC-2176 User property conditions are now marked context-free

This means that user property conditions can be applied to modules that don't have a context, such as general pages. Add-on property conditions are also context-free, whereas all other property conditions require a context. See AC-2176 for more information.

Other Changes

  • CE-709 - (Confluence) the space key is now included in the location context in the JavaScript API.
  • CE-734 - (Confluence) the scrollPosition API was reporting the wrong Y position in Firefox. This has been fixed.

All improvements and fixes

1.2.1

New entity_property_equal_to_context and entity_property_contains_context JIRA and Confluence conditions

In order to solve AC-1608 we have added in two new conditions:

  • entity_property_equal_to_context
  • entity_property_contains_context

These conditions have the following aliases:

  • content_property_equal_to_context (Confluence)
  • content_property_contains_context (Confluence)
  • space_property_equal_to_context (Confluence)
  • space_property_contains_context (Confluence)
  • addon_property_equal_to_context (JIRA and Confluence)
  • addon_property_contains_context (JIRA and Confluence)

This property lets you specify a context parameter, from the current HTTP request, to use for comparison against an entity property. For example, to write a condition that only evaluates to true when a pre-defined project "Scrum Master" is the one making the HTTP request you would write something like this:

{
    "condition": "entity_property_equal_to_context",
    "params": {
        "entity": "project",
        "propertyKey": "teamRoles",
        "objectName": "scrumMaster",
        "contextParameter": "user.key"
    }
}

As you can see, the primary difference between the usual entity property conditions (other than the name of the condition), is that there is no value field and instead that has been replaced with the contextParameter field. In other conditions, the value field must be a JSON literal value; it will be the same value for every HTTP request across all of production and across every tenant. Instead, for this condition, you must provide a valid JIRA or Confluence context parameter inside the contextParameter field and that is the value that will be used for comparison in the condition at runtime. It is important to note that the "Standard parameters" from the context parameters cannot be used here. Only the JIRA or Confluence specific parameters are allowed.

If a given contextParameter cannot be found in the current HTTP request context then the condition will evaluate to false. For example, a condition that asks for the 'user.key' when there is no logged in user will result in the condition evaluating to false.

This condition allows you to have per instance configuration that will let you dictate which modules appear to different users based on contextual information for that request.

1.2.0

AC-1080 Add-ons can act on behalf of users.

This is one of our most requested issues, and we are pleased to announce that add-ons may now perform server-to-server REST calls on behalf of a specified user, using the industry standard JWT Profile for OAuth 2.0 Client Authentication and Authorization Grants.

Read more details on developer.atlassian.com.

All improvements and fixes

1.1.119

New time tracking provider and time tracking conditions

In this version we have added a new module type called jiraTimeTrackingProviders. If declared in your add-on this module is available for selection in the time tracking admin menu and via the time tracking REST API:

Along with the module, we have added 2 new conditions:

  • jiraTimeTrackingProviderEnabled which checks if the JIRA provided time tracking is selected
  • addonTimeTrackingProviderEnabled which checks if a module of type jiraTimeTrackingProvider with the given addonKey and moduleKey is selected

    You can use these conditions to show/hide your web fragments depending on the currently selected time tracking provider.

1.1.107

New entity_property_contains_any and entity_property_contains_all JIRA and Confluence conditions

In order to solve AC-1607 we have added in two new conditions:

  • entity_property_contains_any
  • entity_property_contains_all

That have the following aliases:

  • content_property_contains_any (Confluence)
  • content_property_contains_all (Confluence)
  • space_property_contains_any (Confluence)
  • space_property_contains_all (Confluence)
  • addon_property_contains_any (JIRA and Confluence)
  • addon_property_contains_all (JIRA and Confluence)

These conditions have the same structure as the entity_property_equal_to condition but the "value" field of the condition must be a JSON Array. This is because these conditions perform a "contains" check instead of an "is equal to" check.

The entity_property_contains_any condition will evaluate to true if any of the values in the condition are present in the entity property that it is being compared to. Whereas the entity_property_contains_all condition will only evaluate to true if all of the values in the condition are present in the entity property.

For example, imagine that you stored the following data against a JIRA project under the property key consumingTeams:

{
    "teamCount": 4,
    "teams": ["Legal", "Human Resources", "Accounting", "Taxation"]
}

You could then write a condition to only apply to projects that are for the 'Accounting' and 'Development' teams, like so:

{
    "condition": "entity_property_contains_any",
    "params": {
        "entity": "project",
        "propertyKey": "consumingTeams",
        "objectName": "teams",
        "value": "[\"Accounting\", \"Development\"]"
    }
}

You will note that the value parameter needs to be a string escaped JSON element.

1.1.106

Bug fix for Confluence macro previews

Confluence Macros previews in both macro editor and content preview no longer fail to render. This bug has been present since 1.1.101.

1.1.105

Navigator JS API functionality extended

Functionality added to the navigator method within the JavaScript API. The addonModule route has been added to the navigator, which navigates to a generalPages module as defined by a connect add-on.

1.1.101

1.1.100

1.1.99

Multi-select issue field type

Connect add-ons can define a multi-select type of issue field.

Executed deprecation notice of jsonValue=true field on Add-on Entity Properties resource

This is now the default behaviour of the add-on entity property get request:

GET /rest/atlassian-connect/1/addons/my-plugin-key/properties/my-property

{"key":"test-property","value":{"string":"string-value","number":5},"self":"..."}

You will note that the value field contains a JSON object instead of a string. This deprecation was announced over six months ago and has now been executed.

1.1.97

Bug fix for licensing endpoint

Requests to /rest/atlassian-connect/latest/license no longer fail. This bug was present only in version 1.1.96.

1.1.96

Remote conditions deprecated

Conditions which are evaluated by an add-on service have been deprecated. Remote conditions add a considerable performance penalty to rendering pages. Add-ons using remote conditions should transition as soon as possible to using conditions with entity properties.

For any questions or problems migrating away from remote conditions, please drop us a line in the mailing list and we'll make sure you're covered before remote conditions are removed.

License (lic) parameter now included in web hooks

See AC-1217 for more information.

Number issue field type

A "number" issue field type is now supported.

Default space logos now accessible to Connect add-ons

URLs to download default Confluence space logos are now whitelisted. CE-425

1.1.94

Add support for issue fields

Connect in JIRA now supports adding issue fields via the issue fields module.

Add support for blob filenames for file upload requests

This change is needed since IE and Safari seems to not have a File constructor so the polyfill is used for these browsers. ACJS-239

1.1.90

Shared secret length increased

New installations will now create shared secrets of at least 256 bits. AC-1948

New webhooks in Confluence

Support for two new Confluence webhooks relating to attachments have been added.

  • attachment_trashed: When an attachment is moved to the trash but not deleted.
  • attachment_restored: When an attachment is restored from the trash.

1.1.86

Content properties for Confluence spaces and pages

Confluence add-ons can now store data against spaces and pages and use those properties in conditions. This can be used to eliminate the need for remote conditions. See conditions for more details.

1.1.85

File upload support in JavaScript API

AP.request has been updated to accept object structures, including File objects, when using the multipart/form-data content type.

var fileToUpload = document.getElementById("fileInput").files[0];
AP.require('request', function(request){
  request({
    url: ...,
    type: 'POST',
    contentType: 'multipart/form-data',
    data: {file: fileToUpload}
  });
});

This allows add-ons to use the attachment APIs from JIRA and Confluence.

Define dialogs in the descriptor and open them from the JavaScript API

If you have defined dialog modules in dialogs like so:

"dialogs": [
  {
    "key": "fullscreen-dialog-key",
    "name": {
      "value": "Reusable fullscreen dialog"
    },
    "url": "/fullscreen-dialog-contents",
    "options": {
      "size": "fullscreen"
    }
  }
]

Then you can open that dialog via your add-ons JavaScript by referencing it by add-on module key directly, like so:

AP.require('dialog', function(dialog) {
    dialog.create({
        key: 'fullscreen-dialog-key'
    });
});

This allows you to open dialogs from anywhere in your JavaScript code; you can even open a dialog from within another dialog (nested dialogs are supported).

New E-mail Macro render mode

A new macro render mode has been added to Confluence dynamic macros to aid e-mail notifications.

Confluence dynamic macros can be used to display interactive content and this works well for web pages. However, this does not work (and is often impossible to make work) in other contexts; such as PDF exports and e-mail notifications. For this purpose we provide macro render modes so that when your add-on is asked to render a macro in the context of a PDF export or an e-mail notification you can display meaningful static content.

Here is an example of using the new email macro render mode:

{
  "modules": {
    "dynamicContentMacros": [
      {
        "renderModes": {
          "pdf": {
            "url": "/render-map-pdf"
          },
          "email": {
            "url": "/render-map-email"
          },
          "default": {
            "url": "/render-map-static"
          }
        },
        "url": "/render-map?pageTitle={page.title}",
        "categories": [],
        "outputType": "block",
        "bodyType": "none",
        "aliases": [],
        "name": {
          "value": "Maps"
        },
        "key": "dynamic-macro-example"
      }
    ]
  }
}

Add-on developers can use this feature to ensure that Confluence macro's are rendered nicely in notification e-mails.

1.1.84

1.1.81

Module Descriptor for Dialogs

Dialogs can now be defined as their own modules in the add-on descriptor. A dialog module can be invoked from any number of Web Items, allowing you to specify your dialog in just one place and avoid duplication. For more details, see the Dialog module documentation.

1.1.80

Add-ons REST resource accessible to static add-ons

The REST API, /rest/atlassian-connect/1/addons/{addonKey} can now be reached through the JavaScript API request method.

For an example, see add-ons REST APIs

1.1.78

New onClose trigger for AP.messages

In this release we have added a new callback to AP.messages. You can now register a function which will be invoked when the message is closed.

AP.require("messages", function(messages){
    //create a message
    var message = messages.info('title', 'body');
    messages.onClose(message, function() {
        console.log(message, ' has been closed!');
    });
});

For more details please see the updated messages documentation.

We have also added the ability to hide macro parameters in the macro editor.

For more details please see the Macro Input Parameters.

1.1.77

Overview

  • JIRA and Confluence: New objectName property for entity_property_equal_to conditions AC-1847
  • JIRA: Date picker component ACJIRA-729
  • JIRA: has_global_permission condition ACJIRA-777

New objectName property for entity_property_equal_to conditions

In this release we have updated the entity_property_equal_to condition to make two things possible:

  • Using the objectName parameter you can now compare against a sub-field of an entity property.
  • Comparisons can be performed against non-primitive types; you can now compare two JSON objects.

For example, imagine that you create an issue entity property with the key start-of-justice and the value:

{
  "isJusticeTeam": true,
  "teamMemberCount": 3,
  "teamMembers": ["Manbat", "Superdude", "Wonder person"]
}

Then you could write a condition to ensure that you only show a web fragment when the issue is for a justice team:

{
    "condition": "entity_property_equal_to",
    "params": {
        "entity": "issue",
        "propertyKey": "start-of-justice",
        "objectName": "isJusticeTeam",
        "value": "true"
    }
}

Critically this means that the teamMemberCount and teamMembers JSON fields will be ignored from the perspective of the entity_property_equal_to comparison.

Just as a quick reminder of the comparison rules: all comparisons must be exact, no extra elements. This means that:

  • JSON Primitive types will be compared to in the standard way
  • JSON Array types will be compared to be exactly identical in terms of size and ordering.
  • JSON Object types need to have exactly the same number of fields and those fields need to be identical. Ordering does not matter.

With this new feature you should be able to write useful and powerful conditions against entity properties.

1.1.76

The Navigator Javascript API has been updated so that the navigator.getLocation callback will contain context variables relative to the page currently open in the host application.

AP.require('navigator', function(navigator){
  navigator.getLocation(function(context) {
    // Do something with the context object
  });
});

For more details please see the updated Navigator documentation.

Also, AP.request has been updated to include an experimental field that expects a boolean value. Adding the experimental field to an AP.request will let you make calls successfully to experimental REST API's; this is especially useful if you wish to use some of the latest Service Desk API's. You use the field as follows:

AP.request({
    url: ...,
    ...
    experimental: true
});

1.1.75

New context parameters for conditions

Inline conditions enables the result of evaluating a web fragment condition to be passed as a context parameter to the add-on in an iframe request URL, instead of simply being used to determine whether the iframe should be loaded.

This new feature can be used to avoid making REST API requests on iframe load, or to simplify add-on descriptors that currently contain duplicate modules for the positive and negative results of a web fragment condition.

Dynamic Blueprint Variables

Connect Blueprint Modules have been extended to allow you to define an endpoint on your server that will provide dynamic variable substitution for blueprints as the Confluence page is created. This feature can be used to change a blueprint depending on the user, space, etc. For more information, see this example.

1.1.71

Overview

  • Confluence: Enable chromeless dialogs for custom macro editors CE-283

1.1.69

Overview

1.1.68

New addon_is_licensed condition

In this release we have added in a new condition for JIRA and Confluence. The addon_is_licensed condition can be placed on any Atlassian Connect module that supports conditions. It will evaluate to true if and only if your add-on is a paid add-on and it is licensed. Here is an example of the new condition in use:

"jiraIssueTabPanels": [{
    "conditions": [
        {
            "condition": "addon_is_licensed"
        },
        {
            "condition": "user_is_logged_in"
        }
    ],
    "key": "your-module-key",
    "name": {
        "value": "Your module name"
    },
    "url": "/panel/issue?issue_id={issue.id}&issue_key={issue.key}",
    "weight": 100
}]

In this example the JIRA Issue Tab Panel will only be shown if the add-on is licensed and the user is logged in. There are some caveats to the condition however:

  • If you give away your add-on for free then you don't need to use the addon_is_licensed condition. This is important because all free add-ons are considered unlicensed and will thus the condition will return false. Only use this condition with paid add-ons that are licensed via the Atlassian Marketplace.
  • In local development with the AMPS tools, you will likely not have a license installed that says that your add-on is active. This means that this condition will always return false. Consider only adding the condition to appropriate modules when you know that your add-on will be running on a production Atlassian Cloud instance.

Allow multiple dialogs to be open an the same time

It is now possible open a dialog from another dialog: allowing nested dialogs in Atlassian Connect. The only caveat is that a dialog cannot open another version of itself; this will result in an error being thrown on the client side.

JIRA Agile context parameter changes

Two new JIRA Agile context parameters have been added:

  • board.type
  • board.state

Also, the board.mode parameter has been deprecated in favour of board.screen.

Issues

1.1.67

  • JIRA: Whitelist REST APIs for JIRA Service Desk AC-1774
  • JIRA: Whitelist REST APIs for JIRA Agile ACJIRA-709
  • Allow to pass custom data to the add-on when opening a dialog ACJS-10
  • Fullscreen Dialog with control bar at top ACJS-83
  • Confluence: Add JavaScript API for browser navigation CE-249
  • Add JavaScript API for refreshing the browser CE-249
  • JIRA: Add scope whitelisting for user properties AC-1809
  • Web items with JWTs fail on stale pages ACJIRA-294

1.1.65

  • Add-on Properties GET request can provide the non-escaped JSON value with a query parameter AC-1693
  • JIRA: Added condition to allow a query for available products ACJIRA-590

1.1.64

  • JIRA: Two new modules for you to define global and project permissions for your JIRA add-ons.
  • JIRA Software: The 'agileBoard.id' and 'agileBoard.mode' content properties became the 'board.id' and 'board.mode' content properties respectively. And another JIRA Software content property has been added 'sprint.id'.

1.1.60

  • JIRA: Make jira.openCreateIssueDialog() available on general admin and project admin pages AC-1652
  • JIRA: Fixed issue when installing add-on with ADMIN scope, affecting some versions of upstream services AC-1771

1.1.57

  • Fixed web item actions being broken by certain conditions AC-1640
  • More specific error messages shown for SSL-related installation errors AC-1216

1.1.55

  • Added post-install-page module for add-ons to provide a page with information on getting started AC-1579
  • Confluence: Added fields to the confluenceContentProperties module to allow add-ons to provide aliases for content properties CE-155
  • Confluence: Added support for content property aliases in the UI of the CQL builder CE-156
  • REST endpoint /secure/viewavatar accessible with READ scope AC-1748
  • JIRA: Added field to data-options which hides the footer on an add-on provided page ACJIRA-220

1.1.52

  • Reduce required scope for JIRA project properties to WRITE AC-1686

1.1.48

  • JIRA: Whitelist REST API endpoint for unassigning epic from issues ACJIRA-542

1.1.47

  • Remove OAuth 1.0 as an authentication type in the descriptor AC-1688

1.1.42

  • JIRA: Whitelist REST API for JIRA Agile ACJIRA-491

1.1.41

  • JIRA: Fix issue and project permission conditions AC-1666

1.1.37

  • JIRA: Added ability to open Create Issue Dialog from the add-on ACJIRA-113
  • JIRA: Added API to check if user is allowed to modify the dashboard ACJIRA-436
  • Fix non-responsive dialog chrome buttons when errors from loading content ACJS-44
  • Fixed javascript errors when pressing escape on a non-dialog iframe ACJS-46
  • Confluence: Added scope to create space with an add-on CE-157
  • JIRA: Fixed refreshIssuePage to run on first call AC-1599

1.1.35

  • Fixed broken dialog button callbacks ACJS-41

1.1.33

  • Confluence: Fixed broken generation of macroHash CE-163

1.1.32

  • Add entity_property_equal_to condition for add-on properties ACJIRA-362
  • JIRA: Add entity_property_equal_to condition for project, issue, issue type and comment properties ACJIRA-362
  • JIRA: Provide dashboard items ACJIRA-248
  • Confluence: Add view mode parameter for blueprints CE-110
  • JIRA: Add issue type ID context parameter for issue tab panels ACJIRA-417
  • Confluence: Add macro.id context parameter for macros CE-79
  • JIRA: Whitelist REST API endpoints for dashboard items ACJIRA-247
  • JIRA: Whitelist REST API endpoints for project roles ACJIRA-394
  • Client-side JWT refresh fails for users with UTF-8 characters in the display name ACJS-36
  • Dialog close button doesn't work if there is an error loading the contents ACJS-6
  • Hotkeys cannot be used in dialogs until focused by the user ACJS-22
  • Confluence: : = | RAW | = : parameter causes errors in macros AC-1573
  • JIRA: Admin pages lose navigation context ACJIRA-114
  • Errors in the JavaScript API are swallowed ACJS-2

1.1.29

  • Username and display name available on the JWT token AC-1558
  • Autoconvert: Limiter on number of possible patterns for a single macro

1.1.27

  • Confluence: Allow index schema configuration for content properties CE-77
  • Confluence: Support for extending autoconvert for macros CE-33
  • JIRA: Whitelist REST API methods for JQL auto-complete suggestions ACJIRA-367
  • Improve feedback for failed add-on installations through UPM AC-1547

1.1.25

  • Add REST API for storing and accessing add-on properties ACJIRA-28
  • JIRA: Whitelist REST API methods for comment properties ACJIRA-306
  • Confluence: confluence.closeMacroEditor() stopped working AC-1525

1.1.23

  • JIRA: Fixed broken JavaScript API method - jira.refreshIssuePage() ACDEV-1508

1.1.22

  • Fixed error which prevented web-items with remote conditions from loading AC-1503
  • Confluence: Fixed error which prevented retrieving a macro body by its hash AC-1505

1.1.21

  • Confluence: Added support for render modes for Dynamic Content Macros CE-66
  • JIRA: Added support for aliases in Entity Properties ACJIRA-250
  • JIRA: Added context parameters for Agile Boards ACJIRA-272
  • Improved REST API for license information AC-1370
  • Confluence: Fixed error when inserting Connect macros in Internet Explorer CE-74
  • JIRA: Whitelisted endpoints for thumbnails and user avatars AC-1472
  • JIRA: Fixed has_issue_permission or has_project_permission for web items ACJIRA-263
  • JIRA: Fixed rendering strategy for dialogs when JWT token expired ACJIRA-275
  • Enabled installation of add-ons without modules AC-1439

1.1.18

  • Fixed: Confluence macro editor replaces page content after it gets closed in Internet Explorer

1.1.17

  • Confluence: fixed a bug that made chromeless dialogs fail to display AC-1449
  • JIRA: Expose system properties with REST API: ACJIRA-123
  • JIRA: Whitelist JIRA Agile REST calls for getting epics and adding issues to epics: ACJIRA-219

1.1.15

  • Improvements in lifecycle webhook signatures.
  • Fixed: SSL issues for add-ons hosted on OpenShift.

1.1.10

  • Fixed: add-on loaded twice in the Issue Navigator
  • Fixed: adminpage iframe has padding / margin
  • Send Connect version information to the add-on
  • Scopes white-list JIRA user picker API

1.1.9

1.1.8

  • Fixed: duplicate web panels in JIRA search-for-issues results
  • Fixed: iFrame resizing in Chrome
  • Better error message when group permissions prevent add-on installation

1.1.7

  • Bug fixes and minor improvements

1.1.6

  • More JIRA reports features.
  • Add-ons are no longer automatically uninstalled when the installation lifecycle hook returns an error response.

1.1.4

  • Confluence now supports content.* variables everywhere that page.* variables were supported.
  • Support for JIRA reports
  • Dialogs and inline dialogs will no longer suffer from expired JWTs.
  • Add-ons will no longer change from disabled to enabled as a result of automatic updates.

1.1.0-rc.4

  • Bug fixes and stability improvements

1.1.0-rc.3

  • Read about breaking changes
  • Fixed OAuth authenticated requests
  • Temporarily removed support for Confluence Mobile

1.1.0-rc.2

  • Read about breaking changes
  • Whitelist Confluence Questions context params for webitems and webpanels

1.1.0-rc.1

  • Read about breaking changes
  • JavaScript API: removed deprecated function AP.fireEvent()
  • New feature: condition for checking dark features
  • Fixed: web-sections which rely on add-on-provided web-items fail to register
  • Valid module keys are no longer modified
  • Introduced Confluence Questions content.id / content.version / content.type / content.plugin context parameters for webitems and webpanels
  • Docs: Fix broken links to webhooks module page
  • Docs: web panels are not to be used for dialog content

1.1.0-beta.5

  • Read about breaking changes
  • XML descriptor servlet paths redirect to new JSON descriptor paths
  • Manage cookies through the javascript cookie api
  • Manage browser history through the javascript history api
  • Improve modal dialog, to introduce the chrome flag
  • Dialog height is now always the height of the iframe
  • Refresh a JIRA issue without reloading the page
  • Fixed bug that allowed content to appear in wrong iframe
  • Big speed improvements on add-on install, enable, disable, uninstall etc.
  • Additional REST paths added to scopes and whitelists
  • Add-on keys and add-on module keys have stricter restrictions
  • Fixed numerous workflow post function bugs
  • Improved documentation for workflow post functions
  • Remote web panels fixed in JIRA Agile

1.0.2

  • Fixed workflow post functions
  • Support for hidden macros in the macro browser
  • Removing content from Web-panel no longer leaves grey bar in place

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.