What does it mean for customers?

As of September 18, 2025, Git plugin profiles will stop syncing revisions from connected repositories. Plugins configuration and Source Code tab will be removed.

As of September 18 2025, plugin will stop being available from UI along with Source Code tab.

What customers can do? 

Transition to using new Integrations service with GitLab, GitHub, Azure DevOps, and Bitbucket or use Autmation Rule that will pull commits from Git repo and create Revisions. Next, these Revisions could be pulled out to a new tab instead of Source Code.
On July 17 we release a solution with an Automation Rule sample for linking Revisions to Bugs, Stories and Features.
Solution will not support git users import, comments posting, adding time spent/remaining and state changes – only basic linking of a commit to an entity by ID from commit message.

Will data be migrated from old plugin to new integration service? 

No, the new integration service is configured differently, and setting up the new authorization requires customer involvement as part of the process.

The post Git Plugin Deprecation appeared first on Targetprocess - Enterprise Agility Solution.

As part of the IBM family, Apptio is making some changes to better serve you.  The Apptio Support Portal and Targetprocess Support Portal  are being consolidated into the IBM Support Portal. 

We want to assure you that the same great team will continue to provide support for your Apptio products.

When is the change taking place?

The transition will occur over the third weekend of September beginning at 12:00am EDT Sept. 21 (4:00am UTC Sept. 21).  We anticipate completion on Sept. 23.

What will be migrated?

Cases created after 1 Jan 2023, or closed after 1 Jan 2023, or still open on 21 September 2024.

How do I access my open cases after migration?

If you created an IBMid using the same email address which you used for Targetprocess support prior to the migration, cases you have created can be viewed in the IBM support portal once migration is complete. Please log into the IBM Support Portal once migration is complete to verify access to your cases and reply to any which may be awaiting a response from you. If you are unable to view your cases please refer to the “Where to get assistance for the transition process” section below.

How do I prepare?

Access to the IBM Support Portal requires an IBMid.

If you already have an IBMid, no further action is required at this time.

If you do not yet have an IBMid, you must create one to ensure seamless migration of your existing Apptio Targetprocess cases.  This step should be completed as soon as possible but no later than September 20.  When creating your IBMid, you must use the same email address you currently use for the Targetprocess Service Desk.

1. To create your IBMid go to Create an IBMid. 
2. Fill in the required fields.  Use the same email address you use for Apptio Targetprocess support access. And click Next.
3. If your company already has SSO integration with IBM your account has now been created automatically and you will be logged in immediately.  Proceed to Step 11.
4. Follow the instructions to verify your email address with the 7-digit code emailed to you.
5. Click Create Account.
6. Review the About your IBMid Account page.
7. Click Proceed.
8. Follow the instructions to verify your email (again) with the 6-digit code emailed to you.  This code will be mailed separately from the one used in step 4.
9. Click Verify.
10. You will be logged into the My IBM support page.  Note: You will have no products listed at this time.
11. We recommend enabling the Enhanced Email feature in order to maintain the same case email experience you see today.
    • Go to www.ibm.com/support
    • Click on the person icon in the upper right corner of the page
      
    • Click on Profile & Settings.
      
    • Select the Cases tab
      
    • Check the box for Enhanced Email
      
    • Click the Save button
12. Log out using the person icon in the upper right corner of the page.

Before the transition date, you will not be able to submit Apptio support requests in the IBM Support Portal.  Please continue to submit support requests as you do today via Targetprocess Service Desk or in-app support links. 

Where to get assistance for the transition process?

If you experience issues using the IBM Support Site including creating an IBMid, creating a case, etc; use the Get Help tile on the bottom right to report a problem submitting a case or registering for support. You may be asked for your IBM Customer Number. This can be obtained from your Apptio CSM or account contact.

1. At the bottom of any support portal page, in the "Still have questions?" section, click on "Get help". Not sure if you’re on a support page? Click here
   
2. Below the login prompt, click on the link to "Contact the IBMid help desk".
   
3. On the left menu, click on "Contact support".
   
4. Use the contact email or phone number for your region to get in touch with the IBMid / support portal help desk team.

Using the IBM Support Portal

For quick reference of the process to open, update, and manage support cases refer to the IBM Support Guide.

For detailed introductions on how to interact with the Support Portal please see the links below:

Video resources:

• How to Open a Case (4:31 minutes)
• Profile & Settings (4:08 minutes)
• Managing Support Access (3:05 minutes)
• Sorting and Filtering Cases (3:21minutes)

Online articles:

• How to Open a Support Case
• How to Update Cases
• Adding Users To A Case
• Escalating A Case

FAQ

1. Will I still be able to send an email to tp-support@apptio.com to create a new support request?
   No, new requests can only be created from IBM Support Portal.
2. Do all TargetProcess users in my Organisation need create their own IBMid?
   Every person who wishes to be able to contact Targetprocess technical support team should create their own IBMid.
3. Is Targetprocess Service Desk product affected?
   There are no changes Service Desk product. What is happening is that Targetprocess technical support team will be shutting down their own https://servicedesk.targetprocess.com/ environment of Service Desk and will start managing Targetprocess support cases in IBM Support Portal.
4. Can requesters outside of my organization also have access to the Service Desk?
   Requesters outside of your organization who are used to communicating with Targetprocess technical support team in Targetprocess Service Desk should also create their own IBMid.
5. Are all users and requesters notified by you or should administrators do it themselves?
   Everyone who had raised at least one request with Targetprocess technical support since 01-Jan-2020 was notified.
6. What will happen if somebody will not create an IBMid before the transition date?
   They will not longer be able to:
   • raise a new request with Targetprocess technical support team
   • interact with support on their current open cases
   • view cases submitted in the past
     They will regain all those abilities after they create their IBMid.
7. Do I need to create an IBM Id in order to have the Live Chat service?
   After the migration the Live Chat will be available only from IBM Support portal. Accessing Live Chat will require having IBMid. 
8. Would ideas / feature requests also be migrated to IBM Support Portal?
   No, IBM Support Portal is only used for support cases (questions, issues, incidents).
   From the 23 of September, please use https://ideas.ibm.com/ to post new ideas. Existing ideas will be moved at a later date.

The post Upcoming Transition to the IBM Support Portal appeared first on Targetprocess - Enterprise Agility Solution.

Import forecast

Instructions/ Steps:
1. Type the WIQL (for Azure DevOps) or JQL (if import from Jira) query that defines items you want to import or update with changes from ADO/Jira if they are already imported) and press [Forecast].

Fig 1: Import forecast.

 2. Forecast time shows approximate time based on previous import history. If there were no imports for the past 14 days, approximate time will not be calculated yet. In this case forecasted and remaining time will remain undefined.

Fig 2: Import time estimation.

 3. As soon as you start import, progress will be calculated based on current API responsiveness, Avg.Sync.Time and rate limiting.

Fig 3: Import progress.

 4. Results will show number of imported, updated, or failed items. Failed import could be retried again.

Fig 4: Retry failed import.

Import cancel

Not completed import can be aborted. Import cancellation takes time. It can last for several minutes to stop creating and updating all the items with actual fields values and removed everything that was not actualized.

Items that were updated fully or partially will stay in Targetprocess. Issues imported and yet named like Created by Targetprocess integration service (103084:2eb4df78-9419-4741-97ef-3d0e168cea2b:5eb3dfaa-4013-4615-86bf-de73f8fcabd3) will be removed from Targetprocess as a result of cancelled import.

Instructions/ Steps:

1. Start the import and before it completes, hit [Cancel]
   
2. In a minute you will be able to start new import.

Summary of cancelled import will be delivered in the later releases in June 2024.

The post Integrations with Jira and Azure DevOps: Import Forecast and Cancel appeared first on Targetprocess - Enterprise Agility Solution.

1st Batch of enhancements: Click here to view the Release notes  

2nd batch of enhancements: Click here to view the Release notes 

Release Date: 20 April 2024

Tooltips content now accessible without mouse 

As some users cannot use the mouse effectively, content under the tooltips will now be accessible via keyboard (refer to the image below).   

Focus Indicators on controls

Sighted keyboard-only users rely on visible focus indicators to know where they are on a page. Sometimes these are known as outlines or focus rings. Without focus indicators, it can be extremely difficult to navigate a page. With this release, we are addressing many of the page elements that didn't indicate being focused, and make sure they have visible focus indicators that persist until they are no longer in focus. 

Keyboard navigation for Left Menu

It can be extremely difficult to navigate a through the Left Menu for "keyboard-only" users. Thus to ensure better accessibility, users can now quickly and easily navigate the "Left Menu” via keyboard.

Enhanced contrast on project icons

There are instances of informative graphical elements that have insufficient contrast against background colors, which means users with low vision or color blindness may find it difficult to perceive these important graphics. This release ensures that the contrast between the foreground and background colors of graphical elements that denote projects is at least 3:1. 

Buttons on entity view marked up as buttons

Follow button on entity view is now properly marked up. Disabled controls on customized entity view are now properly marked up for better accessibilty.

The post Keyboard navigation, Better contrast & Tooltip content accessibility – 3rd batch of enhancements under 508 Compliance appeared first on Targetprocess - Enterprise Agility Solution.

Starting from week March 25, you can find additional field 'Secret' in webhook settings of integration profile for Jira Cloud.

This secret must match secret set up in Jira Cloud webhook's settings. If secret in Targeprocess does not match the one in Jira Cloud (or is not added to Targetprocess when it should, or is added to Targetprocess while it's not set in Jira Cloud) then all updates coming from Jira Cloud webhooks will not apply in Targetprocess. Error log will show error for every skipped webhook saying that 'Webhook payload validation failed. Make sure that webhook’s secret in an integration profile matches the one in Jira settings.'

The post Integration with Jira Cloud: Additional Security Secret in Webhooks appeared first on Targetprocess - Enterprise Agility Solution.

Released on: 7 March 2024 

Invalid ARIA roles removed

When screen readers and other assistive technologies do not know the role of each element on the web page, they are not able to interact with it intelligently, nor are they able to communicate the role to the user. An element's features, properties, and methods of conveying information to and/or from the user can't be communicated via assistive technologies when a role value is invalid. Thus, this release ensures that all elements with a role attribute use a valid value.

Use of proper landmark elements

Landmarks such as header, footer, navigation, main, etc. help screen reader users navigate and orient themselves on a page. Also, screen readers announce landmarks so users understand the functionality and context of the content. Sighted users can use location or color information to distinguish these sections of a page. For screen-reader users, landmarks provide this important context.
Thus, proper landmark elements are now used for high-level application structure.

Low contrast on active controls

To support those with low vision, standard contrast to be implemented for active icons and controls. This enhancement ensures that all text elements & icons' contrast is as per the standard - 4:5:1

Detailed View Editor – ARIA roles marked up as per standards

Entity Views are now properly marked up as "dialog". As a result of this enhancement, the screen reader users will be able to access content that is not interactive.

What's Next? 

Upcoming Releases:

1. Proper landmark elements for "Main Search" & "Left Menu": This release will ensure that proper landmark elements are user main search & left menu. 
2. Enhanced contrast on icons
3. Tooltip content to be accessible without mouse: Tooltip contents with help will be keyboard-accessible

The post Enhanced contrast, Landmark elements & Roles marked up : 2nd batch of enhancements under 508 Compliance. appeared first on Targetprocess - Enterprise Agility Solution.

Essentially, it's a procurement tool created by the federal government to guarantee that any information and communications technology (ICT) utilized by federal agencies is accessible to individuals with disabilities throughout its development, procurement, maintenance, and usage. Ensuring web content accessibility for all individuals is a matter of ethics for any organization, regardless of whether Section 508 is applicable. To know more about Section 508 Compliance, please visit: https://www.section508.gov/buy/inventory-your-ict/

Released on: 15 February 2024 

Recent Items support keyboard navigation

Improved navigation for “My Recent” tab. Starting today, users can quickly and easily navigate the “My Recent” pop-up via keyboard. Along with this, the tabs in “My Recent” are now marked up with proper ARIA metadata. Semantic markup is vital for assistive technology users, to convey the structure and relationships between information.  

Steps: 

1. Press the “Tab” key to navigate to the next item of the menu 
2. Press “Shift + Tab” keys to navigate to the previous item.   

 Headings markup – Main App & Settings Page

We have now added HTML heading elements to the heading text. Heading levels are used according to the structural hierarchy of page content, not the visual hierarchy. How does this help? Programmatic headings help assistive technologies provide valuable information to users and deliver content in a smoother experience.  

What's Next? 

2nd batch of enhancements: Click here to check it out 

The post Keyboard Navigation & Semantic Markup – 1st batch of enhancements under 508 Compliance  appeared first on Targetprocess - Enterprise Agility Solution.

• Report from link
• Google Sheets
• GitHub
• Google Analytics
• Trello
• PostgreSQL
• MongoDB
• Jira
• Custom connector apps

Note: If you have existing reports created using data from any external sources, we highly recommend exporting the data as the deprecation can lead to data loss.

The post Deprecated – Reports Connectors appeared first on Targetprocess - Enterprise Agility Solution.

Platform Enhancements

Reports:

• Improved load time for the sample formulas pop-up list during the Report setup.

Other Areas:

• Updates initiated by Automation Rules can now be handled in batches, thereby helping efficient execution.
• Named triggers in Automation Rules can now be activated using the new Save and trigger now UI button.

The following issues have been fixed:

• Issue where hierarchical relations were not being synced correctly on the Parent Link field in Jira DC/Server integration (#743582)

The post Release 2401.4, 2401.5 & 2402.1: Platform Enhancements and Bugfixes appeared first on Targetprocess - Enterprise Agility Solution.

Platform Enhancements

Reports:

• Enhancement to reports by including the option of selecting multiple data fields and adding them into datasets in a single step.

The following issues have been fixed:

Jira, Azure DevOps, GitHub, and ADM Integrations:

• Fixed a few unhandled cases in Azure DevOps integration (#720984)
• Fixed an issue with incorrect mapping in Azure DevOps integration (#735183)
• Fixed an issue with incorrect failure states returned in GitHub integration (#748324)

CSV Import/Export:

• Fixed the issue where the "Save" option was disabled when creating CSV Export profiles and unsaved changes reset (#749093)
• Fixed the issue where CSV Import failed to download ADM dataset in specific cases (#748587)
• Fixed the issue with ExD columns in lists not getting exported to CSV in certain instances (#753178)

Core Functionalities and Other Areas:

• Enhanced the contrast for active UI controls (#730576)
• Fixed the issue where rule engine UI did not display configured erroneous fields present in domain schema (#753254)

The post Release 2401.2 & 2401.3: Platform Enhancements and Bugfixes appeared first on Targetprocess - Enterprise Agility Solution.