Apptio Targetprocess
- Last updated
- Nov 13, 2024
- Save as PDF
- Getting Started
- Installation Primer
- Quick Start Guide
- Key Concepts
- Step 1: Connect to Your Repository
- Step 2: Create or Reuse a Model
- Step 3: Create Your Collection(s)
- Step 4: Configure your Integration
- Step 5: Expand or Modify your Integration
- Configure your Hub to Hub Integration
- Troubleshooting
- Settings
- FAQs
- General
- Tasktop Joins Planview FAQ
- Deprecation of NTLM FAQ
- Does Hub need to be restarted when configuration changes are made?
- Does Hub support artifact deletion across repositories?
- Does Hub support the use of port forwarding/reverse proxies?
- How are users counted in Hub?
- How can I find User Guides for previous versions of Planview Hub?
- How can I learn what transforms are available?
- How does Hub's built-in person reconciliation algorithm work?
- How does Hub change detection work?
- How does Hub determine that a field in project 1 is the same field as in project 2?
- How does Hub handle field values with the same label?
- How does Hub scale to meet Enterprise needs?
- How does Planview ensure security of customer information?
- How do I automate internal workflows using Hub's public API?
- How do I ensure business continuity?
- If a conflict occurs on one mapped field on an artifact, do we synchronize the remaining fields that aren’t in conflict or does that one conflict block the rest of the fields from synchronizing?
- If Comment Flow (or Attachment Flow) is enabled, will only newly added comments (or attachments) sync over?
- If I click 'Process All Artifacts,' what exactly will process?
- What's Different in User Management Workflow with Keycloak Since Hub Version 24.4?
- What's the difference between Continuous Delivery and Long Term Support?
- What are Smart Fields?
- What are the differences between Time Interval and Cron Expression?
- What can I do to lessen the performance impact on my external repositories?
- What does "allow unmapped values to flow" mean for a single select or multi select field?
- What does 'back synchronization' mean?
- What does making a model field "required" mean?
- What does the Hub deployment process look like?
- What do the "special features" mean?
- What is a Concurrency Limit? How does it differ from the Integration Maximum Concurrency Limit?
- What is Planview Hub's underlying architecture?
- What is the difference between 'Process All Artifacts' and 'Initiate Synchronization'?
- When will Planview add or remove support for a repository version?
- Where can I learn about specific connectors like Jira, Jama, etc?
- Why shouldn't I change artifact type in my repository after an artifact has synchronized?
- Installation and Maintenance
- After upgrade, will my integrations automatically resume running?
- Does Planview Hub support Docker? (need to update)
- How can I improve REST API traffic to a repository by using a load balancer?
- How can I increase Hub's session time-out?
- How can I override the default socket timeout for my operational database?
- How can I run Hub on port 443 (the standard SSL port) when I don’t have super user (root) permissions?
- How do I configure Entra managed accounts with Azure SQL in Hub?
- How do I configure Hub to Hub client access?
- How do I configure Hub to use HTTPS?
- How do I configure the max days I'd like to keep Hub log files?
- How do I configure the PlanviewLinkBridgeUser role?
- How do I configure which port Hub uses?
- How do I import my license key into Hub?
- How do I migrate my Hub configuration between databases?
- How do I migrate my operational database from MySQL to PostgreSQL?
- How do I move my Hub Instance to a new server?
- How do I only keep the last two weeks of Tomcat logs?
- How do I prevent vulnerabilities in Windows OS?
- How do I set up Hub to run as a service on Linux?
- How do I upgrade Hub?
- If I forget my master password, how can I remove or change it?
- I’ve forgotten my password to the User Administration Console (Keycloak). How do I get back in?
- What is the Secure Password Storage Security Level and Master Password?
- What practices can I take to reduce "open redirect" security vulnerabilities?
- What should I be aware of when upgrading to 19.2?
- What should I be aware of when upgrading to 19.3?
- What should I be aware of when upgrading to 19.4?
- What should I be aware of when upgrading to 21.1?
- What should I be aware of when upgrading to 23.4?
- Where are the program files, configuration files, and logs for Hub located?
- Where is the context stored for Hub and Keycloak? How can I setup a “persistent volume claim” so that I don’t lose that context when either the Keycloak container or Hub container are restarted?
- Why am I unable to access Hub after bookmarking the login page?
- Troubleshooting
- How can I resolve a "too many files open" error?
- How can I resolve a 'certificate error' in my browser?
- How can I resolve a 'GC overhead limit exceeded (CCRRTT-30000E)' error?
- How do I change Hub's logging configuration?
- How do I troubleshoot in Hub?
- How often and in which interval does Hub retry errors?
- If I delete a previously synchronized artifact in one of my repositories and do not want it to be recreated, is there any way to 'blacklist' it in Hub?
- Log reads “Failed to acquire database lease. The database is in use by another instance of Hub.” What has happened?
- My log files are too big! How can I compress them to save space?
- Where can I find details on errors in Hub?
- Where can I find Hub logs?
- Why am I seeing errors for artifacts that don't even meet my artifact filtering criteria?
- Why do I get a timezone error when creating a database connection?
- Enterprise Data Stream
- Gateway
- Hub on Cloud
- How can I connect Hub Cloud to an On-prem repository?
- How can I resolve certificate validation errors?
- How do I import a CA certificate into my Hub Cloud instance?
- I'm getting a 403 error when I try to log in to my Cloud instance. What should I do?
- Planview Hub Cloud Migration FAQ
- Planview Hub Cloud Security FAQ
- What are the feature differences between Hub Cloud and Hub On-prem?
- What is Hub Cloud's underlying architecture?
- When is my Cloud instance upgraded?
- Connectors
- Can I write information to the Jira sprint field?
- Do I need to perform additional steps for TFS upon upgrading?
- How can I reduce the number of projects shown for Clarity in Hub?
- How can I resolve an error stating, 'Received fatal alert: handshake_failure'?
- How do I create a repository connection to Atlassian Jira On Demand with SSO enabled?
- How do I resolve the 'Too many persons found' error upon integrating with a Jira cloud instance?
- If the PTC Windchill RVS server is localized (i.e., installed on a non-English locale OS), will related objects also need to be localized?
- I received the exception 'PKIX path building failed ... unable to find valid certification path to requested target' when connecting to Team Foundation Server. How do I fix it?
- Jira Epic/Parent Link FAQ
- Jira GDPR Changes
- What happens if the Timesheet Hours per Day field does not match the timesheet configuration?
- Why are there so many files in my temp directory when I use the connector?
- Why do I get authentication errors for ALM/QC when I've correctly entered my credentials?
- Why do I get the error message 'Error while parsing file … expecting Index' while integrating with IBM DOORS?
- Why do I see an error stating 'This method is no longer supported by the catalog service' when querying Visual Studio Online (VSO) or Azure DevOps Services?
- General
- Planview Hub Product Releases
- 25.3 Release Notes
- 25.2 Release Notes
- Hub Release Notes - 25.2.0.20250203-b8396
- Hub Release Notes - 25.2.0.20250306-b8562
- Hub Release Notes - 25.2.0.20250309-b8583
- Hub Release Notes - 25.2.0.20250315-b8615
- Hub Release Notes - 25.2.0.20250323-b8658
- Hub Release Notes - 25.2.0.20250402-b8712
- Hub Release Notes - 25.2.0.20250408-b8745
- Hub Release Notes - 25.2.0.20250417-b8793
- Hub Release Notes - 25.2.0.20250423-b8823
- Hub Release Notes - 25.2.0.20250428-b8844
- 25.1 Release Notes
- Hub Release Notes - 25.1.0.20241126-b8029
- Hub Release Notes - 25.1.0.20241203-b8066
- Hub Release Notes - 25.1.0.20241211-b8109
- Hub Release Notes - 25.1.0.20241230-b8207
- Hub Release Notes - 25.1.0.20250113-b8289
- Hub Release Notes - 25.1.2
- Hub Release Notes - 25.1.3
- Hub Release Notes - 25.1.4
- Hub Release Notes - 25.1.5
- Hub Release Notes - 25.1.6
- Hub Release Notes - 25.1.7
- 24.4 Release Notes
- Hub Release Notes - 24.4.0.20240820-b7489
- Hub Release Notes - 24.4.0.20240829-b7547
- Hub Release Notes - 24.4.0.20240901-b7567
- Hub Release Notes - 24.4.0.20241002-b7743
- Hub Release Notes - 24.4.0.20241015-b7814
- Hub Release Notes - 24.4.0.20241024-b7863
- Hub Release Notes - 24.4.0.20241104-b7916
- Hub Release Notes - 24.4.10
- Hub Release Notes - 24.4.2
- Hub Release Notes - 24.4.3
- Hub Release Notes - 24.4.4
- Hub Release Notes - 24.4.5
- Hub Release Notes - 24.4.6
- Hub Release Notes - 24.4.7
- Hub Release Notes - 24.4.8
- Hub Release Notes - 24.4.9
- 24.3 Release Notes
- Hub Release Notes - 24.3.0.20240504-b6925
- Hub Release Notes - 24.3.0.20240602-b7072
- Hub Release Notes - 24.3.0.20240607-b7098
- Hub Release Notes - 24.3.0.20240609-b7111
- Hub Release Notes - 24.3.0.20240620-b7163
- Hub Release Notes - 24.3.0.20240624-b7184
- Hub Release Notes - 24.3.0.20240701-b7218
- Hub Release Notes - 24.3.0.20240806-b7413
- Hub Release Notes - 24.3.0.20240812-b7446
- Hub Release Notes - 24.3.10
- Hub Release Notes - 24.3.2
- Hub Release Notes - 24.3.3
- Hub Release Notes - 24.3.4
- Hub Release Notes - 24.3.5
- Hub Release Notes - 24.3.6
- Hub Release Notes - 24.3.7
- Hub Release Notes - 24.3.8
- Hub Release Notes - 24.3.9
- 24.2 Release Notes
- Hub Release Notes - 24.2.0.20240205-b6465
- Hub Release Notes - 24.2.0.20240211-b6500
- Hub Release Notes - 24.2.0.20240220-b6547
- Hub Release Notes - 24.2.0.20240227-b6584
- Hub Release Notes - 24.2.0.20240304-b6612
- Hub Release Notes - 24.2.0.20240319-b6692
- Hub Release Notes - 24.2.0.20240323-b6711
- Hub Release Notes - 24.2.0.20240327-b6728
- Hub Release Notes - 24.2.0.20240328-b6740
- Hub Release Notes - 24.2.0.20240405-b6777
- Hub Release Notes - 24.2.0.20240410-b6801
- Hub Release Notes - 24.2.0.20240424-b6872
- Hub Release Notes - 24.2.10
- Hub Release Notes - 24.2.11
- Hub Release Notes - 24.2.12
- Hub Release Notes - 24.2.13
- Hub Release Notes - 24.2.14
- Hub Release Notes - 24.2.2
- Hub Release Notes - 24.2.3
- Hub Release Notes - 24.2.4
- Hub Release Notes - 24.2.5
- Hub Release Notes - 24.2.6
- Hub Release Notes - 24.2.8
- Hub Release Notes - 24.2.9
- 24.1 Release Notes
- Hub Release Notes - 24.1.0.20231015-b5891
- Hub Release Notes - 24.1.0.20231023-b5931
- Hub Release Notes - 24.1.0.20231027-b5963
- Hub Release Notes - 24.1.0.20231108-b6024
- Hub Release Notes - 24.1.0.20231126-b6112
- Hub Release Notes - 24.1.0.20231211-b6183
- Hub Release Notes - 24.1.0.20240107-b6322
- Hub Release Notes - 24.1.0.20240114-b6356
- Hub Release Notes - 24.1.0.20240118-b6377
- Hub Release Notes - 24.1.1
- Hub Release Notes - 24.1.10
- Hub Release Notes - 24.1.11
- Hub Release Notes - 24.1.12
- Hub Release Notes - 24.1.13
- Hub Release Notes - 24.1.14
- Hub Release Notes - 24.1.15
- Hub Release Notes - 24.1.16
- Hub Release Notes - 24.1.3
- Hub Release Notes - 24.1.4
- Hub Release Notes - 24.1.5
- Hub Release Notes - 24.1.6
- Hub Release Notes - 24.1.7
- Hub Release Notes - 24.1.8
- Hub Release Notes - 24.1.9
- 23.4 Release Notes
- Hub Release Notes - 23.4.0.20230710-b5391
- Hub Release Notes - 23.4.0.20230716-b5425
- Hub Release Notes - 23.4.0.20230724-b5465
- Hub Release Notes - 23.4.0.20230731-b5506
- Hub Release Notes - 23.4.0.20230802-b5522
- Hub Release Notes - 23.4.0.20230808-b5548
- Hub Release Notes - 23.4.0.20230814-b5578
- Hub Release Notes - 23.4.0.20230818-b5599
- Hub Release Notes - 23.4.0.20230827-b5635
- Hub Release Notes - 23.4.0.20230903-b5666
- Hub Release Notes - 23.4.0.20230911-b5708
- Hub Release Notes - 23.4.0.20230918-b5748
- Hub Release Notes - 23.4.0.20230925-b5789
- Hub Release Notes - 23.4.0.20231003-b5828
- Hub Release Notes - 23.4.0.20231010-b5862
- Hub Release Notes - 23.4.0.20240208-b102
- Hub Release Notes - 23.4.10
- Hub Release Notes - 23.4.11
- Hub Release Notes - 23.4.14
- Hub Release Notes - 23.4.15
- Hub Release Notes - 23.4.16
- Hub Release Notes - 23.4.17
- Hub Release Notes - 23.4.18
- Hub Release Notes - 23.4.19
- Hub Release Notes - 23.4.2
- Hub Release Notes - 23.4.20
- Hub Release Notes - 23.4.21
- Hub Release Notes - 23.4.3
- Hub Release Notes - 23.4.4
- Hub Release Notes - 23.4.5
- Hub Release Notes - 23.4.6
- Hub Release Notes - 23.4.7
- Hub Release Notes - 23.4.8
- Hub Release Notes - 23.4.9
- Hub Release Notes - 24.1.1
- Tasktop Sync Product Releases
- Planview Hub Editions
- Supported Repository Versions
- Connector Documentation
- Aha!
- Aras Innovator
- Asana
- Atlassian Jira
- Atlassian Jira Align
- Blueprint
- BMC Helix ITSM
- Broadcom Clarity
- Broadcom Rally
- Cherwell Service Management
- codebeamer
- Digital.ai Agility
- Digital.ai Release
- Git
- GitHub Issues
- GitLab Issues
- IBM Engineering Requirements Management DOORS Family
- IBM Engineering Requirements Management DOORS Next
- IBM Engineering Workflow Management
- IBM Rational ClearQuest
- Jama Connect
- Microsoft Azure DevOps Server
- Microsoft Project Server
- Microsoft SharePoint
- Micro Focus ALM Octane
- Micro Focus ALM/Quality Center
- Micro Focus Dimensions RM
- Micro Focus PPM
- Micro Focus Solutions Business Manager
- Mozilla Bugzilla
- Pivotal Tracker
- Planview AdaptiveWork
- Planview AgilePlace
- Planview Enterprise Architecture
- Planview Portfolios
- Planview PPM Pro
- Planview Universal Connector
- Polarion ALM
- PTC Windchill
- PTC Windchill RVS
- Salesforce
- ServiceNow
- SmartBear QAComplete
- Sparx Systems Pro Cloud Server
- TestRail
- Trello
- Tricentis qTest
- Tricentis Tosca
- UiPath Test Manager
- WhiteHat Sentinel
- Zendesk
- Knowledge Resources
- Hub Videos
- Tasktop Customer Portal
_copy.png?revision=1&size=bestfit&width=300)
Overview
Apptio Targetprocess is a visual management tool that was developed in 2004 specifically for agile teams. Nowadays, the software enables organizations of different sizes to apply Agile at the team and project levels, as well as to scale Agile at the program, portfolio and value stream levels.
The tool offers a holistic approach to application lifecycle management (ALM) and project portfolio management (PPM), and eliminates the need for transferring and standardizing data between different management solutions and spreadsheets. When use of a third-party tool is required or preferred by teams, Planview Hub enables seamless and bidirectional integration in order to synchronize artifacts between the multiple tools and infrastructures.
Companies have used Targetprocess to manage software development, track marketing campaigns, run education programs, document internal meetings, and even to test nuclear installations. The tool encourages you to visualize your data from multiple angles in order to get a more comprehensive understanding of your projects, programs and portfolios. Teams and different departments can follow their preferred process while still sending a unified picture up the hierarchy.
Visibility is key in Targetprocess. POs and PMOs conducting planning from a high level can drill down to get details from an operational level. This traceability encourages accountability and transparency across teams and departments. Hub can help to maintain this transparency by keeping all teams on the same page, even if they’re using different tools.
Key Features and Benefits
- Use Hub to keep all teams on the same page, even if they’re working from different tools
- Use Targetprocess to visualize incoming data and act as a central point of truth for your projects or project portfolio
- Eliminates the need to manually create or update work items in other systems or in the Targetprocess boards
- Synchronizes artifacts across the lifecycle allowing free flow of information between Targetprocess and other tools
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
- Providing Testers with Early Visibility into Requirements
- Associating Planning Items to Implementation Artifacts
Demo Videos
Connector Setup Details
This section describes the basic steps needed to prepare your Targetprocess instance for use with Hub. Note that additional fields for synchronization or configuration of queries may be required depending on the requirements of your integration.
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 here for more information on how to create a custom user in Targetprocess.
List of minimal user permissions:
- User should be added to a project in order to access read/write permissions for artifacts within that project.
Connecting to the Apptio Targetprocess Repository
Standard Authentication
Required Fields:
- Location/Connection URL
- Example Format: https://example.tpondemand.com
- Username
- Password
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.
OAuth 2.0 Client Credentials Proxy Authentication
Planview Hub: 24.4 and later
This authentication method enables secure, token-based access via a proxy, using client credentials. Refer here for full details.
Note: Targetprocess does not currently support OAuth 2.0 Client Credentials authentication. As a result, the Targetprocess connector does not allow connecting directly with the Targetprocess repository using the OAuth 2.0 Client Credentials authentication method.
SSO Authentication
Additionally, Targetprocess supports the following SSO implementations:
- Script (HTTP cookies)
- X.509 Certificate
Learn more about how to set up your repository in Planview Hub here.
Other Configuration Settings
Required Relationship Mapping
- Certain artifacts require a “parent” artifact. For example, Tasks must have a parent User Story (otherwise, you will see this error: *CCRRTT000002900E Sync Connector related error. UserStory must be specified. (for Task)). The same is true for Bugs and Tests.
- Other artifact types can be linked via Relations.
Person Reconciliation
For person reconciliation, the following fields are available:
Fields Used for Hub’s Default Person Reconciliation Algorithm |
Field Names for Person Reconciliation Extensions (Note that these are case sensitive) |
Label in Targetprocess |
---|---|---|
ID |
Id |
To find the default ID, open user profile and see the browser tab (see image below) |
Username |
Login |
Login |
|
|
|
N/A |
FirstName |
First Name Note: Due to third party functional limitations within Targetprocess, First Name can be used to reconcile persons flowing outbound from Targetprocess, but cannot be used to reconcile persons flowing inbound to Targetprocess. |
N/A |
LastName |
Last Name Note: Due to third party functional limitations within Targetprocess, ID can be used to reconcile persons flowing outbound from Targetprocess, but cannot be used to reconcile persons flowing inbound to Targetprocess. |
N/A |
Name |
Display Name |
Learn more about how to configure person reconciliation in Planview Hub here.
Comments
Due to a limitation in TargetProcess, Hub cannot synchronize comments as part of standard change detection. To synchronize comments from Targetprocess to a target repository, see the section below.
There are two ways to synchronize comments in TargetProcess:
-
Configure your Hub integration to use a Full Scan Change Detection. This will ensure that all comments will be synchronized.
-
Set up an automation rule in TargetProcess repository to update the "ModifyDate" whenever comments are added/updated/deleted. To do this, use the following steps:
-
Open your TargetProcess instance.
-
Navigate to Settings > Automation Rules > Create a new rule.
-
-
In the JSON tab, paste the following code and click Save.
-
{ "pipeline": [ { "type": "source:targetprocess:EntityChanged", "entityTypes": [ "UserStory", "Request" ], "modifications": { "created": false, "deleted": false, "updated": [ "LastCommentDate" ] } }, { "type": "action:JavaScript", "script": "return {\n command: \"targetprocess:UpdateResource\",\n payload: {\n resourceType: args.ResourceType,\n resourceId: args.ResourceId,\n fields: {\n ModifyDate: new Date()\n }\n }\n};" } ] }
-
-
The provided JSON file includes rules for "UserStory" and "Request" entity types and can be customized as needed.
-
-
This will ensure that comments will be synchronized correctly when there is an update in the “LastCommentDate” or the artifact’s modify date.
-
-
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:
- Attachments
- Assignees
- Relationships (Multi-Links)
- Updating a LinkedTestPlan relationship
Note: Test Plans are available in the Hub UI, but not fully supported by Hub. Please contact support with any questions.
Learn more about how to configure change detection and full scan intervals in Planview Hub here.
Supported Features
Special Features Supported
You can learn more about special features in Planview Hub here.
Feature |
Custom Type Supported? |
Applicable Hub Versions |
Applicable Repository Versions |
---|---|---|---|
|
N/A |
|
|
|
N/A |
Planview Hub: All |
Any supported repository version: |
|
N/A |
Planview Hub: All |
Any supported repository version: |
N/A - State Transitions (Targetprocess does not use state transitions. Status can flow out of or into Targetprocess as a single-select.) |
N/A |
Planview Hub: All |
Any supported repository version: |
Supported Artifacts
Supported Work Items
Learn about the difference between containers and work items in Planview Hub here.
Supported Work Item Type |
Applicable Hub Versions |
Applicable Repository Versions |
Unique URL? |
---|---|---|---|
Bug |
Planview Hub: All |
Any supported repository version: |
Yes |
Feature |
Planview Hub: All |
Any supported repository version: |
Yes |
Task |
Planview Hub: All |
Any supported repository version: |
Yes |
Epic |
Planview Hub: All |
Any supported repository version: |
Yes |
User Story |
Planview Hub: All |
Any supported repository version: |
Yes |
Request |
Planview Hub: All |
Any supported repository version: |
Yes |
Release |
Planview Hub: 19.1 and later |
Any supported repository version: |
Yes |
Portfolio Epics |
Planview Hub: 19.2.0.20190409 and later |
Any supported repository version: |
Yes |
Test Plan Available in Hub UI, but not fully supported by Hub. Please contact support with any questions. |
Planview Hub: All |
Any supported repository version: |
Yes |
Test Plan Run Available in Hub UI, but not fully supported by Hub. Please contact support with any questions. |
Planview Hub: All |
Any supported repository version: |
Yes |
Supported Containers
Learn more about containment in Planview Hub here.
Containers that can synchronize between repositories |
Applicable Hub Versions |
Applicable Repository Versions |
Unique URL? |
---|---|---|---|
N/A |
|
|
|
Containers used to define the boundary of a collection (When clicking 'Manage Projects' on a Collection) |
|
|
|
Projects |
Planview Hub: All |
Any supported repository version: |
N/A |
Containers used for artifact routing |
|
|
|
Projects |
Planview Hub: All |
Any supported repository version: |
N/A |
Supported Field Types
Note: If one field of a given type is supported, others that are also that type in theory should also work. However, sometimes there are instances in which this is not the case due to the repository. So, while we can claim support for fields at the type level, there is a chance that some specific fields of a given type will not synchronize properly.
Standard Field Type |
Does Hub support custom fields of this type? |
How is field type referenced in the repository? |
Sample Repository Fields Supported |
Particular Repository Fields NOT Supported |
---|---|---|---|---|
|
|
Text |
Revision FormattedID |
|
|
|
Drop down list |
Team Release Project Business Value State Type |
|
|
|
Multiple selection list |
Tags |
|
|
|
Check box |
Closed |
|
|
|
Date |
Planned Start Planned End Created Date |
|
|
|
|
End Date Last Comment Date Modified Date |
|
|
|
|
|
|
|
|
Number |
Numeric Priority (read-only) Initial Estimate Effort fields |
|
|
|
|
|
|
|
|
User |
Owner |
|
|
|
Multiple selection list |
Assignments |
|
Learn how to configure relationships in Planview Hub here. |
(Multi-link custom fields only) |
|
|
|
|
|
Rich Text |
Description |
|
|
|
|
|
|
|
|
|
|
|
Functional Limitations
Category |
Limitation |
Applicable Hub Versions |
Applicable Repository Versions |
---|---|---|---|
Third Party API Limitation |
LinkedGeneral Field Use the LinkedGeneral field to flow relationships into Targetprocess and the more specific fields (i.e., LinkedBug) to flow relationships out of Targetprocess. |
Planview Hub: 19.3 and later |
Any supported repository version: |
Third Party Functional Limitation |
Creation Date Field The Creation Date field is writeable only upon artifact creation. |
Planview Hub: 18.3.3+, 18.4.0.20180730 and later (In earlier versions of Hub, Creation Date field is set to date artifact is created by Hub) |
Any supported repository version: |
Third Party Functional Limitation |
Date Fields Targetprocess dates are treated as date fields in the UI, but actually have times associated with them from a technical perspective. Values set to the EndDate field in the UI are given a time of 23:59, one second before the next day, presumably to signify the end of the day. Depending on the time zone of the server, this could cause date fields to synchronize as the following day into the target repository. |
Planview Hub: All |
Any supported repository version: |
Third Party Functional Limitation |
'IsReplied' Field The 'IsReplied' field (on Targetprocess requests) is writable by Hub, but can be overwritten by Targetprocess depending on who logged the most recent comment. If the most recent comment was made by a Requester (rather than a User), IsReplied will be set to F. If a Targetprocess user then comments on the request, it will be set to T. |
Planview Hub: All |
Any supported repository version: |
Third Party Functional Limitation |
'Last Comment Date' Field The 'Last Comment Date' field is writable by Hub. However, Targetprocess will overwrite that value with the date of the most recent comment whenever a new comment is created. |
Planview Hub: All |
Any supported repository version: |
Third Party Functional Limitation |
Requester Field A 'requester' cannot be set in the Assignments field. Attempting to do so via person matching will result in an error from Targetprocess with a message such as, "User with ID ___ could not be found." |
Planview Hub: 18.2 and later |
Any supported repository version: |
Third Party API Limitation |
Time Fields To write to the Time Spent and Time Remaining fields, the "No time calculation" metric must added be in the Metrics section of the settings, for the processes and types the user would like to write to. To enable this feature, please contact Targetprocess support. |
Planview Hub: 18.1.12 and later |
Any supported repository version: |
Third Party API Limitation |
Effort and Progress Fields To write to the effort and progress fields (Progress, Effort, EffortCompleted, and EffortToDo), the "No effort calculation" metric must be added in the Metrics section of the settings, for the process and types the user would like to write to. To enable this feature, please contact Targetprocess support. |
Planview Hub: 18.1.12 and later |
Any supported repository version: |
Third Party Functional Limitation |
Effort and Progress Fields The Progress field in Targetprocess is a calculated field (calculated as a proportion between Effort To Do, Effort Completed, and Effort). However, it is possible to set the value for the Progress field directly via Hub, so long as the effort fields are not also modified. Therefore, your Hub integration should either write to the effort fields or the progress fields, but not both. |
Planview Hub: 18.1.12 and later |
Any supported repository version: |
Third Party Functional Limitation |
Effort Fields Effort field values set during synchronization will be overwritten or cleared by effort roll-up that occurs in Targetprocess when State is changed or when a child Entity (ex. a Task on a User Story; a User Story on a Feature) is added, removed, or when a child Entity's effort field values are changed. |
Planview Hub: 17.2 and later |
Any supported repository version: |
Best Practice |
Configuration Under Assignments, users should be assigned to their own Role if available and the first available Role otherwise. The same user should not be assigned more than once on an Assignable. Otherwise the synchronization may move Assignees to different Roles within Assignments and duplicate Assignees may be removed in order to meet these conditions. |
Planview Hub: 17.2 and later |
Any supported repository version: |
Third Party Functional Limitation |
Impersonation Artifact impersonation is not supported. |
Planview Hub: All |
Any supported repository version: |
Third Party Functional Limitation |
Comments Empty, synthetic, and private comments are not supported. |
Planview Hub: All |
Any supported repository version: |
Third Party Functional Limitation |
Creator Field Creator field is not supported. |
Planview Hub: All |
Any supported repository version: |
Third Party API Limitation |
Requester and Owner Fields In TargetProcess, the first (or only) person in the "Requesters" field takes precedence over the "Owner" field when a TargetProcess Request is created. If both an "Owner" and a "Requester" were specified when creating a Request, the actual owner would be the "Requester". Note this side-effect is only present when creating a Request artifact. If you update the Requesters field on an existing Request artifact, TargetProcess does not change the "Owner" field value. Finally, this behavior is only witnessed for "Request" artifacts. This is not a general limitation for other TargetProcess artifact types. |
Planview Hub: All |
Any supported repository version: |