PMIS Configuration

Overview

Project Management Information System (PMIS) integrations allow Decisions to connect with external project tracking systems, such as Jira and Azure DevOps. These integrations are used to import external work items into Decisions as user stories and to support sprint-based development and deployment tracking.

PMIS connections are configured on the Deployment Server from System > Integrations > PMIS. After a PMIS connection is configured, sprints and user stories can be imported from the external PMIS system into either the Deployment Server or the connected Development Server. Imported items are synced between the Deployment Server and Development Server to support project tracking and deployment workflows.

Configuring a Jira PMIS Connection

Use a Jira PMIS connection to import Jira work items into Decisions as user stories.

To configure a Jira PMIS connection:

1. On the Deployment Server, navigate to System > Integrations > PMIS.
2. Create a new Jira connection.
3. Provide the required connection details:
   1. Name: A display name for the connection.
   2. Base URL: The Jira site URL for the organization.
   3. Email or Username: The Jira account used for authentication.
   4. API Token: A Jira API token generated for the account. For more information, see Manage API tokens for your Atlassian account.
4. Click Test Connection. The connection must be successfully tested before it can be saved.
5. Save the connection.
   

Configuring an Azure DevOps PMIS Connection

Use an Azure DevOps PMIS connection to import Azure Boards work items into Decisions as user stories.

To configure an Azure DevOps PMIS connection:

1. On the Deployment Server, navigate to System > Integrations > PMIS.
2. Create a new Azure DevOps connection.
3. Provide the required connection details:
   1. Name: A display name for the connection.
   2. Organization URL: The full Azure DevOps organization URL.
   3. Personal Access Token (PAT): A token generated from Azure DevOps for authentication. For more information, see Create a personal access token.
4. Click Test Connection. The connection must be successfully tested before it can be saved.
5. Save the connection.

Active PMIS Connection Behavior

Only one PMIS connection type can be active at a time. For example, if a Jira PMIS connection is marked as Active, an Azure DevOps connection cannot be active at the same time, and vice versa.  

Importing Sprints and User Stories

After a PMIS connection is configured on the Deployment Server, sprints and user stories can be imported from the external PMIS system into Decisions. Imports can be performed from either the Deployment Server or the connected Development Server. This allows teams to import PMIS work items from the context they are working in while keeping the Deployment Server and Development Server aligned.

After sprints are imported or available in Decisions, user stories can be imported into the target sprint and used for development and deployment tracking.

For detailed steps, see the following documents:

• Importing Sprints from PMIS
• Importing User Stories from PMIS