ThoughtWorks Mingle

Technical requirements

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

  • Basic authentication must be enabled for Mingle.

  • A service user account is required to connect to Mingle.

    • The service account must have permission to create issues and update issue status in each target project

Default assigned fields

The following fields are set by default:

  • Name

  • Description

Behavior

The integration supports the following:

  • Two-way status synchronization

Connection details

Enter the connection details for the server.

Protocol

The method to connect with the server (Default: HTTPS)

Server

The domain name or IP address of the server

Context Root

Normally left empty unless the service is installed at a non-standard location

Credentials

Enter the credentials needed to authenticate to the server.

Username

Username authorized to connect with the server and having permission to create issues in anticipated Mingle projects.

Password

The password used to authenticate to the server

Tasks to Synchronize

Select tasks to synchronize.

Sync all tasks

Synchronize all tasks from Mingle.

Sync Risk Policy tasks

Synchronize only tasks that fall under the risk policy.

Project details

Enter the project-level details.

Mingle Identifier

The name of the project where issues should be created.

Advanced Mingle configuration

Card Type

(Default: Story)

Open a story in Mingle with the following status

(Default: New)

States which map to DONE in SD Elements:

(Default: Complete)

Synchronization

Enter settings for synchronizing SD Elements tasks.

Authoritative Source

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

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

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

Include code sample How-To’s in task descriptions

Indication whether code samples are copied to Mingle

Filter tasks

Select SD Elements tasks to synchronize to Mingle.

Tasks having a minimum priority

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

Tasks with status meaning

Only synchronize tasks with certain statuses, such as TODO or DONE. (Default: TODO)

Limit to tasks having these phases

Only synchronize 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

Only synchronize tasks containing certain SD Elements task tags. (Optional)

Tasks with verification status

Only synchronize 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 cetain value. This is applicable only when custom titles are selected having the entry 'Context'

results matching ""

    No results matching ""