The following features were introduced or enhanced in Agile Manager 2.42:
See also: What was new in previous releases
You can now view, edit, and filter by a backlog item's Kanban lane outside the Storyboard:
The Lane field is available in the Details view, and you can also add the Lane column to the Sprint Backlog grid.
Note: The Kanban statuses are defined per team, therefore:
- In the Details view, the Lane field is relevant only if the backlog item is assigned to a team.
- The Lane is available only in the Sprint Backlog, which is based on per-team data.
When you use the Kanban Storyboard, you will find a smoother user experience and improved performance.
For example, you no longer have to select a field by which to filter.
When you type freely in the filter box, the Storyboard displays only items whose Name, ID, or Assigned To fields contain any of the words you typed!
In grids: You can now filter for empty values in date columns. Select No Value in the filter's drop down.
In the Add New dialog for features: To prevent the list of themes from being filtered according to the Application you select, select the Show all check box near the Theme box.
You can now edit the alternate root folder defined in Release or Requirement synchronization links. However, you should edit this path only if the folder in ALM was renamed. Do not enter a different alternate root folder.
When mapping field values, we added some helpful abilities:
If you map a field that is mandatory in the destination endpoint with a field that is optional in the source endpoint, errors may occur during synchronization.
If the optional field is empty, synchronization will fail when Synchronizer tries to create a new entity that contains the mandatory mapped field.
To prevent such errors, define a default value that Synchronizer can enter in the mandatory field in this situation.
Note: Synchronizer uses the default value only when creating a new entity, not when updating.
Map numbers to strings or lists.
You can now map numeric fields in one endpoint with string or list fields in the other endpoint.
If... Then... If you map a string field in the source endpoint with a numeric field in the destination endpoint For the synchronization to succeed, the string field value must be an integer. If you map a numeric field in the source endpoint with a list field in the destination endpoint
For the synchronization to succeed, the numeric field value must be one of the values in the list.
Note: In ALM, a list field can be defined no to verify values. In this case, a numeric field mapped to the list can contain values that are not in the list.
Map empty values.
When you map specific field values for list fields, you can now map one of the values to an empty string.
On the Site > Fields configuration page, we added the feature Owner field. You can now define it as required for all new features.
On the Site > Users configuration page, administrators can now see more details about licenses and their expiration dates.