The following features were introduced or enhanced in Agile Manager 2.33:
Site administrators can now define User Story, Defect, and Backlog Item custom fields as required. This adds the required field to the Add Item dialog box, forcing users to define a value for a required custom field when first creating new user stories or defects.
Required fields are indicated in the Add Item dialog box with a red asterisk (*).
Additionally, required custom fields are indicated on the Fields configuration page in the new Required and Displayed in Add Dialog columns.
Browse to the Site > Fields configuration page, and add or edit a User Story, Defect, or Backlog Item field.
In the Add or Edit Field dialog box, select the Mark this field as required option.
To view an example, click the image on the right.
Custom field requirements are enforced only when adding or importing new items in Agile Manager. They are not required when updating existing items, synchronizing items with ALM, or adding items using the Agile Manager API.
Defining fields as required per site is supported only for custom fields. Administrators cannot modify requirement settings for out-of-the-box system fields.
Maximum number of required fields
A maximum of 15 fields can be displayed in the Add Item dialog box for each entity type, including out-of-the box fields displayed by default.
Once this maximum is reached, you cannot define any more fields as required for that entity type.
Setting a Backlog Item field as required counts towards the maximum for both user stories and defects.
Importing items with required fields
If you import user stories or defects to Agile Manager, you must add additional columns to the import files for any custom fields marked as required, using the exact field names.
You may want to mark these extra columns as required by adding a comment to the column header, and save the file as a template for later use.
- We changed the name of the page from Custom Fields to Fields.
- On this page, we added support for sorting and filtering columns. Enter text or use the drop-down menu to filter a column. Double-click a column header to sort the grid by that column.
Site and workspace administrators are now able to view the individual users currently logged in to Agile Manager.
On the Site or Workspace > Users configuration page, view a user's current login status in the new Logged In column.
To view an example, click the image on the right.
When working with ALM 12.20, ALM Synchronizer for Agile Manager can connect to ALM using SiteMinder single sign-on (SSO) or smart card authorization.
To use this feature, you do not need to upgrade your Synchronizer.
When using external authentication, entity links cannot be synchronized.
Linked entities will remain linked in their original endpoint, but the links will not be synchronized to the other endpoint.
In a synchronization link, when providing ALM credentials, use a user name that is not an email address.
To enable external authentication connections, you must do the following:
On the ALM server
Configure the user that Synchronizer uses to connect to ALM so that it can log in using a name and not only an email address.
For details, see the ALM Administrator Guide.
On the Synchronizer server
Make sure that the Synchronizer server service is not run by the default Local System user. Instead, it must be run by the same Windows user who installed the Synchronizer server.
You can check and edit this in the Windows Services dialog box. The service name is similar to HPE Application Lifecycle Management Synchronizer.
Caution: The same Windows user must be the one to install certificates and run the Webgate Customization tool in the following steps.
If you are using Smart Card authentication, install the SmartCardUser certificate on the server:
Save the certificate to a file named server.cer, in the <Synchronizer installation>\java\bin directory.
Tip: If the SmartCardUser certificate is a PFX file, you can use the Microsoft Management Console to import it, and then export to a cer file.
Use the keytool command from the <Synchronizer installation>\java\bin directory to import the server.cer file to the <Synchronizer installation>\java\lib\security\cacerts directory.
keytool.exe -import -v -trustcacerts -alias tomcat -file server.cer -storepass <password> -keystore <Synchronizer home>\java\lib\security\cacerts
Using the Webgate Customization tool:
On both the Web Server Settings tab and the Proxy Settings tab, configure access to ALM using external authentication from the Synchronizer server, by defining ALM server and Proxy server credentials.
For details, see the ALM External Authentication Configuration Guide.
Configure an authentication proxy for Agile Manager. For details, see Configure an authentication proxy.
Disable linked entity synchronization.
Add the following option to the server.properties file located in the <Synchronizer installation directory>\dat folder:
- Restart the Synchronizer server.
See also: Create a synchronization link
Developers using our Agile Manager API can now interact with Agile Manager directly from our API Interactive Help.
Explore supported entities and operations, or enter a client ID and secret to request data from Agile Manager.
Access the Interactive Help from the Agile Manager Help menu (Help > API Interactive Help), or as a Site Administrator from the Integrations > API configuration page.
In the API Interactive Help:
To perform interactive operations, at the top of the page, enter your client ID and secret, and then click Authenticate.
Note: You can view available resources, operations, and parameters even without entering credentials. You must enter credentials only to submit operations.
Expand unique and general resources and operations for more details about each one.
The timesheet resource is a unique resource, with operations specified for generating timesheet data.
Workspaces, releases, and backlog_items are general resources, all with the same operations.
For each operation, enter parameter values in Value column fields, as described in the Description column.
Click Submit to perform the operation using the parameters you've specified, or copy examples or syntax into your code.
Caution: POST and PUT operations performed make actual modifications in your data, such as adding or editing backlog items or releases.
For this reason, we’ve disabled the Submit button for certain operations, such as Delete, to prevent you from making irreversible changes via the API Interactive Help.
See also: API Interactive Help
The Agile Manager API now supports the backlog_items resource, allowing developers to get lists of backlog items, as well as create, update, and delete individual backlog items via API.
The backlog_items resource includes two subtypes: user_story and defect. Each subtype supports different fields and parameters.
To view the full list of parameters for each subtype, including any custom fields added to your site, submit a GET operation with a query to filter the response by subtype.
For example, use the following query:
You can manage backlog items directly from our new API Interactive Help, as shown in the image above, or by copying examples from our interactive help into your code.
If you are new to the Agile Manager API, a site manager must provide you with a client ID and secret that Agile Manager generates for your application.
Note: To support the new backlog_items resource, we added the new API ID field to user stories and defects. Use this field value to reference specific items.
We redesigned our Help Center with fresh colors and web-friendly, top-navigational layout.
In Agile Manager, select Help > Help on This Page for details about the page you're looking at.
Use the drop down menus at the top to navigate to different areas of the Help Center, and links on the left to navigate to topics in the same area.
Search using filters for the main area of Agile Manager only, or one of our synchronization tools.