No-code integration platform for rich bi-directional sync
Zero downtime migration to tool of your choice
Keep Historical Data, Without Slowing Down Your Tools
Migrate or restructure Azure DevOps Instances
Real-time, context-rich data lake for AI or analytics
By Role
Accelerate delivery with clear insights
Transform smarter with a connected digital thread
Confident transitions for every enterprise change
By Initiative
Modernize and move to cloud without disruption
Build a compliant digital thread for complex environments
Build the foundation for smarter AI
By Domain
No-code integration across teams & systems
Enable collaboration between IT, support & business teams
Connect PLM & engineering teams for smarter products
Ensure regulatory compliance from start to release
Explore the latest in technology and best practices
Success stories from the field
Actionable insights for your business challenges.
See solutions in action
Learn, plan, and execute with confidence
Official announcements and updates
Join discussions that drive results
Stay ahead with curated insights
The defense industry is entering a pivotal phase with the introduction of DoDI 5000.97, mandating the shift to Digital Engineering (DE). This article examines the challenges, including tool interoperability and data governance, and how suppliers can adapt through Intelligent Federation and integration platforms like OpsHub.
Development and customer support teams often face challenges in prioritizing the most essential and critical fixes and enhancements from the customer standpoint. By improving cross-functional visibility between ALM tools such as TeamForge and ITSM tools like ServiceNow, teams can work on the most important features and defects, releasing high-quality products faster. Integrating TeamForge with ServiceNow using OpsHub Integration Manager (OIM), development and support teams can achieve near to real-time visibility into status, activities and issues within and across projects. This helps solve customer issues faster, increasing team productivity and efficiency. In the first phase of this video, we will demonstrate how to create and bidirectionally synchronize an enhancement request created in ServiceNow to TeamForge. In the second phase, we will show how a problem logged by the customer related to the same enhancement request is seamlessly solved by the support team in ServiceNow and the Development team in TeamForge. Take a look!
Schedule a 30-minute live demo with our integration experts
TeamForge is an ALM platform for traditional and hybrid software development, delivery, and collaboration. It reduces IT support costs and drives standardization and IP reuse. By integrating TeamForge with other tools in the software lifecycle, teams can build an integrated pipeline from planning through deployment to deliver high-quality products to customers at a faster pace.
OpsHub Integration Manager supports the integration of TeamForge with 60+ ALM, DevOps, ITSM, and CRM systems. In this video, we will showcase how OpsHub facilitates the integration of TeamForge with ServiceNow.
The support team in ServiceNow creates an enhancement request, adds descriptions, priority, and status, and saves it. The enhancement request synchronizes to TeamForge as a feature, providing the development team with visibility into the feature they need to work on. The enhancement request created in ServiceNow is successfully reflected in TeamForge along with all its details, including the remote ID and remote link.
The development team in TeamForge now starts planning the feature, adding a clarification question in the form of a comment for the support team in ServiceNow. In ServiceNow, the support team reviews the comment added by the development team, which has synchronized successfully, and adds a reply and an attachment for clarification. Both the comment and the attachment added in ServiceNow are bidirectionally synced to TeamForge. This bidirectional synchronization enables the support and development teams to collaborate effectively on feature clarification.
In TeamForge, the development team refreshes the page to view the attachment and comment added in ServiceNow and then changes the status to Pending and saves it. The development team in TeamForge now starts breaking the feature into two user stories. The development team adds the first user story, gives it a title, description, and dependencies, and creates a parent-child relationship. The first user story is successfully created, and the development team similarly creates the second user story.
As the user stories are created, the QA team in TeamForge gains visibility into them. In ServiceNow, the status changes made in TeamForge are successfully reflected along with the two user stories. Back in TeamForge, the development team changes the status of both user stories to indicate to the QA team that they are ready for testing. The status changes made in TeamForge are successfully reflected in ServiceNow.
In TeamForge, the QA team starts adding test cases. For the first test case, the QA team adds a title, description, and dependencies to create a parent-child relationship and similarly adds the second test case. Both test cases are successfully created. The QA team changes the status of the test cases to “Passed” after fulfilling the expected results.
The development team then navigates to the feature and changes the status to “Closed”, indicating completion of the feature. This change automatically synchronizes back to ServiceNow. Finally, in ServiceNow, the development team refreshes the page to view the synchronized status of the user stories as “Resolved” and the status of the enhancement request as “Closed”. This completes phase 1 of the demo, where we showed the creation and bidirectional synchronization of an enhancement request from ServiceNow to TeamForge.
In phase 2 of the demo, we will show how a problem logged by the customer related to the same enhancement request is seamlessly resolved by the support team in ServiceNow and the development team in TeamForge. The customer in ServiceNow creates an incident ticket. The support team in ServiceNow clicks on the ticket, verifies all details, identifies the issue, adds a comment asking the customer for additional details, and saves it.
The support team in ServiceNow creates a problem ticket from the incident ticket, adds descriptions, sets the priority to “High”, updates the status, and links the problem ticket with the enhancement request by providing the ticket number in TeamForge. The problem created in ServiceNow synchronizes successfully as a defect in TeamForge along with all its details. This defect in TeamForge can be traced back to its associated feature under Associations.
The development team in TeamForge analyzes the issue and adds a comment as a reply, requesting additional details. In ServiceNow, the support team reviews the comment added by the development team in TeamForge and replies with a comment. The comment added in ServiceNow is bidirectionally synced back to TeamForge. In ServiceNow, the support team navigates to the incident ticket to find the customer’s comment and additional details as requested, downloads the attachment, and adds a reply to the customer.
The support team then changes the status of the incident to “Active “and saves it. The support team navigates to the problem ticket and attaches the additional details received from the customer along with a comment notifying the development team of the same. The details and comment added in ServiceNow automatically synchronize back to TeamForge.
The development team in TeamForge refreshes the page to view the synchronized attachment and comment and adds a reply to the support team in ServiceNow. The development team starts working on the defect, changes the status to In Progress, sets a completion date, and saves it. The status change and due date set in TeamForge successfully reflect in ServiceNow, providing the support team with clarity and visibility into the release date and progress of the problem. The comment added in TeamForge also reflects in ServiceNow.
In TeamForge, once the fixes are completed, the development team adds a comment and changes the status of the defect to “Closed”, indicating its resolution. Back in ServiceNow, the support team refreshes the page to view the updated status of the problem ticket as “Closed” along with the comment. Finally, the support team navigates to the incident ticket to notify the customer of the resolution and changes the status to “Closed”, indicating closure of the incident ticket.
This completes the demo. Thank you for watching.
Schedule a 30-minute live demo with our integration experts
