HP ALM

Technical Requirements

The following requirements must be met to integrate HP ALM with SD Elements.

  • HP ALM version 11.50 or 12.x

  • SD Elements should have network connectivity to the HP ALM server

  • SD Elements authenticates to HP ALM using a normal HP ALM user. Therefore, a HP ALM service user account is needed. The service account must have permission to create issues, and update issue status, in each connected project.

  • Access to the following modules:

    • Requirements Module

    • Test Plan Module

    • Test Lab Module

Default-assigned Fields

The following fields are set by default:

  • Description

  • Priority

Behaviour

The integration supports the following:

Connection details

Enter the connection details for the server.

Protocol

Select the protocol for the connection (HTTPS or HTTP) (Default: HTTPS)

Server

The domain name or IP address of the server (Example: hpalm.server.com)

Context Root

Top-level location where HP ALM is installed on a server. The value for this may be dependent on the configuration of an internal corporate proxy or where an administrator has installed HP ALM.

Credentials

Enter the credentials needed to authenticate to the server.

Username

Username authorized to connect with the server

Password

The password used to authenticate to the server

Tasks to Synchronize

Select tasks to synchronize.

Sync all tasks

Synchronize all tasks from the server.

Sync Risk Policy tasks

Synchronize only tasks that fall under the risk policy.

Project details

Enter the project-level details.

HP ALM Project

The name of the project where issues should be created.

Advanced HP ALM configuration

Issue Type

(Default: Functional)

States which map to DONE in SD Elements:

Comma-separated list of states in HP ALM that will be mapped to DONE in SD Elements. (Default: Passed)

Open a story in HP ALM with the following status

Status to assign to new issues in HP ALM (Default: Not Completed)

Reopen a work item in HP ALM with the following status

Status to use to open a closed issue in HP ALM (Default: Not Completed)

Close a work item in HP ALM with the following status

Status to use when closing issues in HP ALM (Default: Passed)

Domain

The HP ALM Domain associated with the project

Test plan folder to import test tasks

Folder to receive test tasks (Default: SD Elements)

Default type for test plans

The type given to new test plans (Default: MANUAL)

Synchronization

Enter settings for synchronizing SD Elements tasks.

Authoritative Source

Select the tool that will be the authoritative system of record: HP ALM or SD Elements. This field is used in case of conflicting statuses between the Github issue and the SD Elements task. When you first synchronize a TODO task in SD Elements with an issue in Github, they will have the same status. If you then change the status in one tool, for example by closing the issue in HP ALM, they will have conflicting statuses. This conflict is resolved when the projects are synchronized. There are two options:

  • ALM (default): The SD Elements task will be updated to match the status in HP ALM. This is relevant to most workflows.

  • SD Elements: The HP ALM status will be updated to match the SD Elements status.

Include code sample How-To’s in task descriptions

Whether or not to include detailed code samples and How-Tos in the HP ALM issue.

This server is not accessible from the SD Elements server

Select this option if SD Elements does not have direct network access to the HP ALM server. For example, if you are using a hosted SD Elements instance but you want to integrate with an internal/protected HP ALM system, choose this option and run the Remote Integration Client to perform integration.

Tasks to synchronize

Select which SD Elements tasks to synchronize.

Tasks having a minimum priority

Synchronize tasks with a minimum priority (for example, 7 or above). This is useful if you want to limit the amount of work for users. (Default: 1)

Tasks with status meaning

Synchronize only tasks with certain statuses, such as TODO or DONE. (Default: TODO)

Limit to tasks having these phases

Synchronize only tasks in certain phases, such as Requirements or Development. (Default: none selected, meaning tasks from all phases will be synchronized)

Tasks having all of the following tags (optional)

Synchronize only tasks containing certain SD Elements task tags.

Tasks with verification status

Synchronize only tasks with a specific verification status, such as Pass or Fail. (Default: none selected, meaning tasks with any verification status will be synchronized)

Advanced ALM options

Enter advanced configuration options.

ALM context

Bind a set of tasks using a certain value. This is only applicable when custom titles are selected with the entry "Context"

Custom Fields Mapping

In addition to the default-assigned fields, you can map additional SD Elements fields to HP ALM fields.

 Fields that are not required or have default values do not need to be set.

For example, you may have a required field in your HP ALM project that is not set by default. Custom field mappings can be set at both the system connection and project connection levels, and that mappings set in a project connection will override mappings set in the system connection.

For more details refer to section Advanced field support.

Sync frequency

Select how frequently the SD Elements and HP ALM projects are synchronized. You can choose from the following options. The more frequently you run synchronization, the greater the performance impact on both the SD Elements and HP ALM servers. This is generally only a concern for large organizations running many synchronizations at once.

Hourly, Daily, Weekly, or Monthly

The projects will synchronize automatically every hour, day, week or month. Daily synchronization is typically sufficient. However, you may want to select a more frequent interval if development moves quickly in your organization.

Manually

You must click the Sync button on the ALM Integrations page in order to synchronize the projects. This is the default value.

results matching ""

    No results matching ""