Trello

Key Features and Benefits

Integration helps flow cards and updates to cards between Trello and all the other tools in your software delivery toolchain. The seamless flow of data eliminates the waste and overhead endemic in project management and cross-team collaboration, including duplicate data entry, status meetings and chasing down information. In the software delivery context, Trello is commonly integrated with “downstream” tools used by product managers, developers, testers and release managers to implement the details of a project. Most often Trello is integrated with Agile planning tools (Jira, Azure DevOps, Digital.ai Agility) and issue tracking tools (GitHub, GitLab, ServiceNow).

Common Integration Patterns

• Associating Planning Items to Implementation Artifacts
• Associating Planning Items to Requirements
• Providing Developers with Early Visibility into Requirements
• Associating Requirements to Detailed Design

Demo Videos

Custom Fields Power-Up

Retrieval of values specified with Trello's built in Custom Fields power-up is supported.

Hello Epics Power-Up

Retrieval of 'children' relationships via Trello's Hello Epics power-up is supported.

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 Trello Help to learn how to create a new user.

List of minimal user permissions:

• Administrator of a team on the board(s) being synchronized.

All other users being synchronized will need to either be a member of a team on the board(s) being synchronized, or a member of the board(s) being synchronized.

Connecting to the Trello Repository

Token Authenticator

Required Fields: 

• Location/Connection URL 
  • This will always be https://api.trello.com/
• API Key: An API key associated with the user you would like to use.
• Token: An authentication token associated with your API key.

Optional Fields:

• Throttling Settings: This field indicates the number of API calls that can be made per minute. See details here.
  • 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.

SSO Authentication

Additionally, Jama supports the following SSO implementations:

• Script (HTTP cookies)
• X.509 Certificate

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

Rich Text

Supported rich text elements are: 

• Headings
• Code
• Lists
• Paragraph
• Quote
• Anchor
• Emphasis
• Strong

Attachments

In Trello, 'Attachments' can be split into many different types, which are treated differently by Hub:

Hub differentiates Trello 'Attachments' into three categories:

• Attachments: These are files uploaded to Trello after selecting 'Attach from Computer.'  These are what will flow when you choose to flow attachments as part of your integration.
• Relationships: These are relationships to other Trello cards (not boards) created when you select 'Attach from Trello.' These will be treated as 'Related To' relationships in your Hub integration. 
• Web Links: These are URLs to third-party file services, Trello boards, or arbitrary links added by the user when selecting 'Attach from Google Drive, Dropbox, Box, Onedrive, or Trello (when selecting a board),' the 'Attach a link' text box, etc. These URLs will be handled by Hub as Web Links.

The Trello connector can retrieve the following metadata when flowing attachments out of Trello:

• Date
• Author
• File Name
• ID
• Location
• Size

Learn more about how to configure attachment flow in Planview Hub here.

Person Reconciliation

For person reconciliation, the following fields are available:

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

Full Scan

Due to third party API limitations, updates to the following fields may not trigger change detection or cause a synchronization immediately.  To ensure these updates synchronize, a high fidelity full scan must occur or another qualifying change must be made to the artifact:

• "Subscribed" Boolean Field

Learn more about how to configure change detection and full scan intervals 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.