Planview AgilePlace

Key Features and Benefits

• Improved visibility into the overall status of projects by using boards to visualize overall project status and WIP (work in process).
• Eliminates the need to manually update the virtual boards, or use brittle point to point integration techniques.
• Synchronizes artifacts across the lifecycle allowing free flow of information between AgilePlace and other tools.
• Allows you to implement Lean software methods across your project or just within discipline or team.

Common Integration Patterns

• Sharing Stories and Defects between Dev and Test
• Providing Developers with Early Visibility into Requirements
• Aligning Testing Teams across Testing Tools
• Populating Requirements into PLM Tools

Demo Videos

Minimal User Permissions & Hub User

We recommend that you create a new user within your external tool, to be used only for your Hub integration. This is the user information you will enter when setting up your repository connection within Planview Hub. By creating a new user, you will ensure that the correct permissions are granted, and allow for traceability of the modifications that are made by the synchronization. 

In general, your user account should have sufficient permissions to create, read, and update artifacts in your repository. However, depending on the use case, your user may need different permissions. For example, if you are only interested in flowing data out of your repository, your user may not need to have full CRUD access, as the 'create' and 'update' permissions may not be needed.

Your user should have a secure password or token. Please be aware that Hub will not allow you to save a repository connection utilizing a weak password/token, such as 'tasktop.'

See AgilePlace help documentation on how to create a custom user in your repository. 

Create a AgilePlace user account to be used by Hub and ensure that:

• User must be an account administrator.
• User must be able to create and update artifacts in the AgilePlace boards to be synchronized.
• Users should be added to the list of users of a board (Board Settings > Board User Access).

Connecting to the Planview AgilePlace Repository

Standard Authentication

Required Fields:

• Location/Connection URL
  • Example Format: https://server.leankit.io/
• Username
• Password

Optional Fields:

• Use Card Type as Artifact Type (Deprecated): This setting defines how card types are differentiated.
  • Enable this setting to expose card types as different artifacts (legacy behavior, deprecated).
  • If disabled (default), there will be only one artifact type ('Card') available, and card types will be exposed via a separate field.
• Throttling Settings: This field indicates the number of API calls that can be made per minute. 
  • By default, AgilePlace has a limit of 160 API calls per minute for each user account. When setting up your AgilePlace repository, a recommended setting for this field is 144 API calls per minute. If you experience performance delays, this limit can be raised with assistance from customer care. If your user account rate limit is raised or lowered, you will need to change the setting in the Hub configuration to always be slightly lower than the limit defined by AgilePlace. See details below.
  • Note: This field should only be set under the guidance of customer care as the ideal value is highly dependent on each customer's unique environment. 
• Connection Security: If checked, insecure connections to this repository will be allowed. See details here.

API Token Authentication

Required Fields:

• Location/Connection URL
  • Example Format: https://server.leankit.io/
• API Token

Optional Fields:

• Use Card Type as Artifact Type (Deprecated): This setting defines how card types are differentiated.
  • Enable this setting to expose card types as different artifacts (legacy behavior, deprecated).
  • If disabled (default), there will be only one artifact type ('Card') available, and card types will be exposed via a separate field.
• Throttling Settings: This field indicates the number of API calls that can be made per minute. 
  • By default, AgilePlace has a limit of 160 API calls per minute for each user account. When setting up your AgilePlace repository, a recommended setting for this field is 144 API calls per minute. If you experience performance delays, this limit can be raised with assistance from customer care. If your user account rate limit is raised or lowered, you will need to change the setting in the Hub configuration to always be slightly lower than the limit defined by AgilePlace. See details below.
  • Note: This field should only be set under the guidance of customer care as the ideal value is highly dependent on each customer's unique environment. 
• Connection Security: If checked, insecure connections to this repository will be allowed. See details here.

OAuth 2.0 Client Credentials Proxy Authentication 

This authentication method enables secure, token-based access via a proxy, using client credentials. Refer here for full details. 

Note: AgilePlace does not currently support OAuth 2.0 Client Credentials authentication. As a result, the AgilePlace connector does not allow connecting directly with the AgilePlace repository using the OAuth 2.0 Client Credentials authentication method. 

Learn more about how to set up your repository in Planview Hub here. 

Creating a Clickable Card Header that Links to the Target Artifact

By taking advantage of AgilePlace's custom card ID functionality, you can set up your integration to provide a clickable link on the AgilePlace card that will redirect you to the corresponding artifact in your target repository.

The example below walks through how to configure a clickable link on your AgilePlace card that will send you to the corresponding Jira issue.  

First, custom card ID settings should be set up as follows: 

• Enable header
• Display text from unique card ID
• Generate a link from the custom card ID

  • The link structure should mirror the URL structure in your target repository (Jira, in this example), including '{ID}' as a placeholder for the unique ID in your target repository.

Within Hub, configure your Field Mapping so that it contains a one-way field flow from Jira Key (Formatted ID) → AgilePlace Card ID (customID).  

This will enable LeanKit to store text in the header that contains a hyperlink pointing to the Jira target artifact:

Relationships between 'Cards' and 'Tasks' 

For person reconciliation, the following fields are available:

Learn more about how to configure person reconciliation in Planview Hub here.

Special Features Supported

Supported Work Items

Learn about the difference between containers and work items in Planview Hub here. 

Supported Containers     

Learn more about containment in Planview Hub here.