The Agile Manager API now supports the following new general resources, which developers can use to get lists of Agile Manager items, as well as create, update, and delete individual items via API:

• themes

• features

• tasks

• sprints

• release_teams

• team_members

release_teams and team_members resources represent pairing of releases to teams or teams to members. These resources do not contain data related to the releases, teams, or members.

This supports:

• Releases containing multiple teams

• Teams assigned to multiple releases

• Teams with multiple members

• Users belonging to multiple teams

Use the API Interactive Help ( Help > API Interactive Help) to learn more about these resources.

This Agile Manager version includes a new version of the Integration Bridge, and supports synchronizing with ALM 12.50 using NextGen Synchronizer.

Any existing bridges automatically detect the need for upgrade and the following takes place without your intervention:

• The existing bridge is disabled.

  

• The new version of the Integration Bridge is downloaded and verified.

• The new bridge is installed in place of the existing one and enabled (retaining any relevant configuration).

In the future, you can receive email notifications at the beginning and end of automatic upgrades.

Configure the Integration Administrator users that will receive upgrade notifications (Integrations > Synchronizer configuration page, Notification tab).

Configure your Integration Bridge to use OAuth authentication when connecting to Agile Manager.

When using OAuth:

• Your Integration Bridge does not access Agile Manager using user credentials.
• The bridge is not affected by user password expiration.
• The bridge does not consume an Agile Manager license.

For new bridges:

1. On the Integrations > API configuration page, add an Integration Bridge client.

   Note: This step must be performed by a Site Administrator.

   Agile Manager generates a client ID and secret for the bridge.

   

2. Install the Integration Bridge and use the client ID and secret for the credentials that the bridge uses to connect to Agile Manager.

For existing bridges:

The bridge will continue to connect to Agile Manager using the previously defined username and password, and not OAuth, until one of the following occurs:

• You manually update the bridge to use OAuth:

  1. On the Integrations > API configuration page, add an Integration Bridge client. Agile Manager generates a client ID and secret for the bridge.

     Note: This step must be performed by a Site Administrator.

  2. Run the bridgeAuthentication command line tool to modify the credentials that the Integration Bridge uses to access Agile Manager.

     For the credentials, use the client ID and secret that were generated in the previous step.

• The password of the Integration Bridge user expires.

  Caution: When this happens, the bridge will stop working until you update the bridge to use OAuth. To avoid password expiration causing bridges to go offline unexpectedly, we recommend updating your bridges to use OAuth before their passwords expire.