Note: Before you can work with the PPM Pro - LeanKit integration, your PPM Pro administrator and Planview Customer Care need to set up the integration. Please check with your administrator to be sure that everything is in place. If you do not see a field called "Sync with LeanKit" in your project Details or Settings, then your system setup may not be complete, please submit a Support Case with Customer Care.
Users of the integrated projects will continue to use PPM Pro and/or LeanKit as they normally would. This document calls out any caveats, gotchas, and subtleties to be aware of when using the integrated tool of choice.
See also the FAQ later in this topic.
Agile Management with LeanKit and PPM Pro
The relationship between PPM Pro and LeanKit allows you to create work in PPM Pro or LeanKit, bi-directionally synchronize and manage that work, and report out on that work in PPM Pro. Key to successful agile management is using the right tools for the right job - tools that are flexible and can evolve as you hone your processes. For example, a common division of labor is to use PPM Pro for project planning phase and to use LeanKit for the project execution phase. In this scenario, developers are provided with one place to look for work (LeanKit), whose cards link back to the PPM Pro project that is driving the work. As your developers get comfortable and creative with LeanKit, they can evolve the original lanes, or boards, or workflow to better suit their needs, all while keeping the flow of information back to the project.
All descriptions of how the integration works are predicated on the integration being active, and appropriate and correct configuration of both LeanKit and PPM Pro, as described in Setting up the PPM Pro - LeanKit Integration (v2).
PPM Pro and LeanKit work together at the project/task/issue and card levels; for example, the creation of a new project in PPM Pro can result in the creation of a corresponding LeanKit card on a specified LeanKit board. Any configured project tasks and/or issues result in corresponding LeanKit cards, with appropriate connections to designate parent relationships (hierarchy). If tasks are repositioned in the synced work breakdown structure (WBS), LeanKit cards are automatically "re-parented".
Conversely, you can drop a LeanKit card in a "work-creation-enabled" lane to automatically create a PPM Pro project based on an associated template; any tasks/issues included in the template will be created in PPM Pro, which results in the creation of tasks/issues cards back in LeanKit. Note that PPM Pro project templates themselves cannot by synced. Your admin can set up project categories to include standard and custom fields that can be mapped to LeanKit fields of the same type. For example, you can include the project Start Date on your project detail, and map it to LeanKit's Planned Start Date field. Data flows between mapped field fields in both directions, meaning that if you edit a field in one tool, it will update the other.
Once a card is created LeanKit, it's business as usual: you can manage it as you would any other card (change priority, enter description, add child cards, change lanes, move to another board, and so on). Same for PPM Pro projects - once a project is created in PPM Pro, you can manage as you would any other project. Same for tasks and issues.
The key thing to remember about working in an integrated PPM Pro -> LeanKit environment is that you DO NOT talk about the INTEGRATED ENVIRONMENT...oh wait, that's Fight Club :) Actually the thing to remember about working in an integrated environment is not to be surprised if you see changes to field data, or card positions, or card titles, and so on. You might see changes to resource assignments or project ownership, or the task WBS. Do not be alarmed.
The rest of this topic includes information we thought might useful to end users, and includes a FAQ section.
From LeanKit, drop a card into an enabled LeanKit lane to create a project in PPM Pro). If the LeanKit resource who dropped a project card in the work creation lane is not found in PPM Pro (email not in both systems), then the project template owner will be the project owner (project templates are required for work creation). If the email exists in PPM Pro, then that user becomes the project Owner.
From LeanKit, click on the "lane-enabled" icon to popup a modal that tells you what kind of project will be created as a result of dropping the specific card type in the enabled lane. Example shown below:
- From PPM Pro, when creating a synced project in PPM Pro (resulting in a card in LeanKit), the system requires an owner, so no mapping is necessary; LeanKit does not require a card owner.
- Project owners must be users; task and issue owners can be resources.
- From PPM Pro, if you don't want a project to sync, don't enable the "Sync with LeanKit" setting.
- PPM Pro project templates cannot be synced.
- Tasks - if you want task cards to appear as tasks in PPM Pro, the card must have a parent card that is a synced task or the synced project card, and the card type must be synced to a task category. In PPM Pro, a child task will not sync unless the parent task is also set to sync.
- If you don't want a task card to be synced, do not make it the child of a synced element, or do not use a card type that is synced.
- If you have a task in PPM Pro that you don't want synced, use a task category that is not synced to a card type.
- NOTE: The Task elements within a LeanKit Card cannot be synced to tasks in PPM Pro; only LeanKit cards can be synced to tasks in PPM Pro.
- Project log parent must be the synced project card and the card type must be synced to a project log category.
- If you don't want an issue card to be synced, do not make it the child of a synced element, or do not use a card type that is synced.
- If you have a project log in PPM Pro that you don't want synced, use a task category that is not synced to a card type.
Syncing Assigned Resources/Users
Resources can be tasks/issues owners. If you plan to sync resources between LeanKit and PPM Pro, best practice is to make sure your PPM Pro resources match your LeanKit resources (exist in both systems, with same email address).
Project owner has to be a user, tasks and issues owners can be resources.
Deleting Synced Elements
If a project is deleted, its associated cards will remain on their LeanKit board(s) (will not be deleted).
If you delete synced LeanKit tasks, they will be recreated the next time the project syncs.
For LeanKit cards, the URL to the corresponding PPM Pro element is displayed in the External Link field
New LeanKit cards always appear in the drop lane, you can move them around as you need to
When you create a card in LK w/out parent, will put at end of wbs.
Use the connections of the cards to information the outline of the work breakdown structureExample - Task status field is required, but will be in an error state (won't accept changes) until you give a value
Q1. How do I know if the integration is available?
A: From PPM Pro, look for the "Sync with LeanKit" setting - either on project Details, Settings, or Additional Details sections.
From LeanKit, go to Board Settings and look for the Planview Sync section.
Q2. How do I know if a lane is enabled?
A: Look for the "enabled" icon shown below. This icon appears on any enabled lane. Further, you can click on the icon to see what card triggers the creation of PPM Pro project based on the specified project template.
Q3. Why does my assigned resource go away in LK or PPMP?
A: With synced entities, assigned resource emails need to appear in both PPM Pro and LeanKit. If a resource is a user in LK, but is not a resource in PPM Pro, the LeanKit user will be removed whenever that card is next synced.
Q4: Why did my card Title get truncated?
A: LeanKit card titles are limited to 64 characters; PPM Pro entity titles are 80 characters. If a synced project is created in PPM Pro with a title greater than 64 characters, then the Leankit card that is created will truncated title (64 characters and an ellipsis). Note that the card will immediately sync back to PPM Pro, where the truncated title will update the project title with the truncated version.
Q5: When I create work from LeanKit, how is the project owner determined?
A: The project owner is either the resource who last modified the card (either by creating it in the enabled lane or moving it into the enabled lane), and if that resource's email does not exist in PPM Pro, then the Owner of the project template will be the Owner of the project.
Q6: My LeanKit fields are not updating.
A: Check that your LeanKit default board still exists. If this board is deleted, the integration will be interrupted and PPM Pro will no longer be updated. If you are suspicious the board is deleted, check and see if Sync with LeanKit is still enabled - it becomes disabled if the default board is deleted.
Q7: All my LK fields disappeared.
A: Ask your admin to check that the integration has not been disabled.
Q8: I have a custom field and it has no value (it did previously)?
A: If you move a card from one board to another, custom field data does not transfer with it (and won't be synced because effectively it is a different field).
Q9: have an ongoing maintenance project (no real end date), and I really only want to work with the cards linked to the project, but not the project itself. For example, we have a sustaining board that we use to process defects and enhancements.
A: We put the project itself in a "Placeholder" or "Ongoing" lane and just deal with the child cards.
Q10. I deleted a card from my LeanKit board, but it keeps reappearing.
If you delete a card type that is synced to a task category, the card will be recreated (the next time the task is synced). Workaround is to contact PM and ask them to delete the task from PPM Pro.
Q11. I have an existing project that I created before the LK V2 integration existed. How do I integrate it?
If you have existing projects that you want to use with LeanKit, simply change the project's category to use one configured for the integration. Add the Sync with LeanKit field to the project's Details, enable it and click Save.