NextGen Synchronizer now supports synchronizing past and current releases, including sprints/cycles.

1. Plan your synchronization:

   • Check for releases that already exist in both endpoints, and understand how to synchronize them correctly.

   • Optionally, create a sub-folder in the ALM Releases folder, to use as an alternate root folder.

2. Create a release synchronization link, and define the relevant rules and settings.

   

This version of NextGen Synchronizer requires a manual upgrade of the Integration Bridge. Future upgrades will take place automatically.

This version also includes the following abilities:

• Synchronize Agile Manager with ALM version 12.21.

• Connect to ALM using LDAP or SiteMinder single sign-on (SSO).

• Install the Integration Bridge on Linux or Windows systems.

• On Windows, set up a non-admin user to run the Integration Bridge and Endpoint Credentials Manager.

Export: You can now include tasks and acceptance tests when exporting backlog items to Excel from the Release Backlog, Product Backlog, and Defect Management.

Import: When you import backlog items from an Excel file, you can now include tasks and acceptance tests.

Create a Tasks sheet for defects and user stories, and an Acceptance Tests sheet for user stories.

Associate tasks and acceptance tests with backlog items, by adding an ID column to the Backlog Items sheet and a Backlog Item ID column to the Tasks or Acceptance Tests sheets.

For assistance, use the import template files available from the Agile Manager Help.

Define system fields as required

Site administrators can now define system fields as required, in addition to custom fields.
These field requirements are enforced when adding items using the Add Item dialog box, when importing backlog items, and when converting user storied to features.

The Fields configuration tab now displays built-in system fields as well as custom fields. You cannot delete system fields, but you can define them as required.

Some system fields are always displayed in the Add Item dialog box. This is indicated in the Displayed in Add Dialog column and cannot be modified.

• These fields are included in the 15 fields that the dialog box can contain.
• For each field, you can specify whether the user is required to define a value.

Define required fields for themes and features

Site administrators can now define required fields for new themes and features, in addition to user stories and defects.
These field requirements are enforced only when adding themes and features, and when converting user stories to features.

• Enhance your Agile Manager integration with other tools via API.

• The new Application and Team API resources enable you to create a more robust integration with Agile Manager data.

• The Backlog Item and Release resources now support all CRUD operation on Attachments as well.

• Use the API Interactive Help to learn more about how to use these new abilities.(Help > API Interactive Help)

When you View change history, you can now view changes that were made to the Description field.

You can now use the Advanced Settings when customizing your Release Forecast graph. This enables additional filtering options, display options, and more.

Themes filtered by selected application

When you add a new Feature item, select an application.

The list of themes is now limited to those relevant to the selected application.

Attachment field included in Add Item dialog in Internet Explorer

The Attachment field is now included in the New Item also when you work in Internet Explorer.

Browse to select an attachment, or drag an attachment into the field.

Our Help Center is now available online: https://admhelp.microfocus.com/agm.

• Opens directly from the Agile Manager Help menu.
• Shows up in Google search results.

Starting with version 2.41, Agile Manager will no longer officially support working with Internet Explorer 9.

This means:

• Functionality that was available in version 2.40 will continue to function.
• Newer functionality might not operate correctly on Internet Explorer 9.

We recommend migrating to a supported browser version before then for continued support.

Supported browsers: Chrome, Firefox, and Internet Explorer 10 and above.

See also: Internet Explorer Support Lifecycle Policy FAQ