Kovair is now part of SurgeONE.ai Same experts, even more power.

Month: July 2019

Kovair Azure Integration Adapter helps the Azure tool to take care of the deployment process after the developer checks in a code file to the Source Control Repository.

Using XML programming language, developers can use the adapter to directly re-route the checked-in code file from the SCM and then deploy it in Azure tool.

Kovair Omnibus works as the central platform of data flow and exchange between all ALM tools. When integrated with the adapter, it can expand the benefits of Continuous Deployment and Delivery (CD) by automating the flow of software build files to the deployment tool thereby hastening the release process of the software.

Key Highlights of Kovair-Azure Adapter

  • Universal Language of Communication between Tools
    Kovair-Azure Adapter enables the Azure tool to communicate with other ALM tools using the standard XML programming language.
  • Centralized Data View of Azure Reports
    Users can stream data reports from multiple Azure instances and view it from Kovair Platform. Such as line graph reports of ‘Http Error Requests’ of websites hosted in Azure for last 24 hours, ‘Average Response Time vs. CPU Time’ of a Web App Service created in Azure, ‘Inbound vs Outbound’ data of a Web App deployed in Azure for the last 24 hours.
  • End-to-End Data Traceability
    The adapter can expose entities and the data related to these entities directly from the tool to Kovair Omnibus. As a result of the integration, data can be visible from other ALM tools that are integrated to the Kovair platform. In addition, it could also be used for creating progress report graphs.
  • Direct Deployment Actions
    The adapter enables users to take command of any deployment action like Start/Stop/Restart/Publish, directly through Omnibus.

Features & Benefits

  • Synchronizes Azure tool with testing and defect management tools to automate testing of deployed build files through provisions.
  • Supports the best practices of software delivery like streamlining resource allocation to achieve Continuous Integration, Continuous Testing, and Continuous Delivery.
  • Enables users to take command of deployment actions in Azure like Start/Stop/Restart.
  • Enables one to track Application Deployment Result, Component Deployment Result, and their interrelationship including relevant fields like the Request ID, Deployment Status.
  • Ensures direct tracking and monitoring of deployed objects in Azure from Omnibus and other ALM tools.  
  • Enables Release Managers to view status of deployed applications from Kovair Omnibus or other ALM tools that are connected to it.
  • Caters to the Azure deployment setup containing other existing builds.
  • Web based codeless configuration screens for easy configuration and customization.
  • Unidirectional synchronization of released deployments with corresponding segments, tasks, and their mutual relationship. 
  • ESB based integration with SCM tools that offers direct access to Deployment information and Release configurations in Azure from respective tool IDEs.
  • End-to-end traceability of the Deployment process and the tasks corresponding to it.
  • Push button deployment process that removes manual effort and recovers the wasted resource time.

Benefits of Kovair Dynatrace Adapter

  • Track Alert:  With the integration in-place using Omnibus IT team can centrally track and manage alerts & notifications on application health and critical business transactions based on the rules defined for threshold.
  • Code level Diagnostics:  As part of performance testing, it provides ability to determine which transaction is slow, and helps us in identifying the reasons for slow transaction by allowing to drill down to the method in code causing issue and helps in isolating the performance bottlenecks.  All the critical transactional can be traced intimated to the respective team.

Services Supported in Kovair Dynatrace Adapter

Exposed Entities Events Collected Actions Supported Relations Supported
  • Subscription
  • Resource Group
  • App Service
  • Activity Log
  • Monitor
  • Deployment
  • Supports basic events like Add and Edit.
Supports actions like Start, Stop, Restart, Publish, and Deploy.
  • Subscription ID to Resource Group
  • Subscription ID to App Service
  • Resource Group to App Service
  • Subscription ID to Activity Log
  • Subscription ID to Resource Group to Activity Log
  • App Service to Monitor to Activity Log
  • Deployment to Activity Log
  • Change of Status/ Addition of New Event to Activity Log

Azure Integration Usecase

Kovair-Azure Continuous Deployment begins once the code files are fetched from the version control repository hosting service (example – GitHub) to facilitate the technical aspects of continuous delivery.

To understand the Kovair Azure deployment process, let us consider a scenario wherein a requirement is created by logging into a Requirement Management (example – IBM RRC) tool. When the tool is integrated with the Omnibus Enterprise Service Bus, all the logged in requirements will become traceable from Kovair platform as well as from other ALM tools that are connected to it. Similarly, based on these requirements when a build is triggered, all the corresponding Applications, Components, and Deployment processes that are configured in Azure, will automatically become traceable when the Azure adapter is used to integrate the tool with Kovair platform.

Azure Integration Usecase

Users of Kovair can directly fetch the artifacts from the control repository (example – GitHub), trigger a build using a build tool (example – Jenkins), test the build file using testing tool (example – Selenium), and Start/ Stop/ Restore/ Publish to deploy it on to the staging and production server using the Azure tool. During the process of deployment, all data related to the individual deployed components, their completion and status would become directly traceable from Kovair platform. In case of any unsuccessful deployment, that is, if a particular build component fails to pass the Selenium test, Kovair’s Traceability View can easily point out the incorrect version of the deployed code and quickly modify it with a correct version. When the deployment process is successfully complete, a deployment success notification will be automatically updated inside Kovair Omnibus. This notification will also be visible from inside the Selenium tool, following which, the QA team can execute regression tests based on previously created test cases. Kovair-Azure integration offers complete managerial traceability across the whole deployment process. It minimizes the manual task and reduces the frequency of errors in an otherwise repetitive process.


Note: The adapter as developed and offered by Kovair follows the subject tool’s standard specifications. Any deviations from the Tool’s typical use pattern may not have been anticipated in our off-the-shelf product. For any customization or special configuration needs, please contact Kovair Sales – sales@kovair.com

Dynatrace is an Application Performance Monitoring (APM) tool to analyze the performance of application servers, database servers, and web services.

Kovair Dynatrace Integration Adapter

Kovair Dynatrace Adapter’ allows one to integrate Dynatrace tool with best-of-breed ALM tools within Omnibus ecosystem. As a result of the integration, metrics monitored from Dynatrace tool can be traced and analyzed in Kovair or any analysis tool.  This integration brings Kovair DevOps solution to capture application performance data as well as data related to network, containers, servers, hosts, cloud.

Features & Benefits

  • Synchronize attributes related to Problem and Event from the Dynatrace tool to target tools.
  • Continuously monitoring user experience is essential to getting timely insights on usage trends, response times and overall user satisfaction
  • Real-time metrics based on events, transaction health across different platforms, response error, etc.
  • DevOps must strike a balance between velocity and stability. Dynatrace integration brings   the innovation, performance, and availability to take care of the challenge efficiently

Benefits of Kovair Dynatrace Adapter

  • Track Alert:  With the integration in-place using Omnibus IT team can centrally track and manage alerts & notifications on application health and critical business transactions based on the rules defined for threshold.
  • Code level Diagnostics:  As part of performance testing, it provides ability to determine which transaction is slow, and helps us in identifying the reasons for slow transaction by allowing to drill down to the method in code causing issue and helps in isolating the performance bottlenecks.  All the critical transactional can be traced intimated to the respective team.

Services Supported in Kovair Dynatrace Adapter

Exposed Entities Supported Events
  • Problem
  • Event
  • Supports basic events like Add and Edit for all entities.

Use Case Scenarios with Kovair Dynatrace Adapter

Let us consider a typical use case scenario where the Kovair Dynatrace tool is integrated with tools like Remedy/Service Now, JIRA, Eclipse, GitHub, Jenkins, and Kovair application using Kovair adapter for Dynatrace and Kovair Omnibus.

Use Case Scenarios with Kovair Dynatrace Adapter
  • Step 1: A ticket is raised in Remedy/ServiceNow. This ticket becomes available at JIRA as backlog by Kovair
  • Step 2: Either all backlog items or based on certain condition some backlog item will be made visible in Eclipse by Kovair
  • Step 3: Inside eclipse, developers will work with BDD Swift, App Builder and App Swift.
  • Step 4: Once coding is done, the code will get checked in to GitHub.
  • Step 5: Once the code is checked in to GitHub, Jenkins will be invoked from Kovair.
  • Step 6: Jenkins will do the build, deploy the build in staging server and will invoke test automation using Selenium.
  • Step 7: If test automation is successful then build gets deployed in production by Kovair Omnibus as a continuation of step 5 else the build is not deployed in production and user is informed about the decision.
  • Step 8: Once the build is deployed in production, application monitoring is done using Dynatrace. The monitoring results are then pushed into Kovair Omnibus. Based on different predefined conditions or rules, corresponding tickets would be created in Remedy/Service Now system by Kovair. Mails can also be another form of events/trigger. Corresponding tickets would be created in Remedy/Service Now system by Kovair.

Note: The adapter as developed and offered by Kovair follows the subject tool’s standard specifications. Any deviations from the Tool’s typical use pattern may not have been anticipated in our off-the-shelf product. For any customization or special configuration needs, please contact Kovair Sales – sales@kovair.com

Microsoft Exchange Server is Microsoft’s email, calendaring, contact, scheduling and collaboration platform deployed on the Windows Server operating system for use within a business or larger enterprise.

Kovair Microsoft Exchange Server Integration Adapter

Kovair adapter for Microsoft Exchange Server helps to leverage the Omnibus architecture and facilitate collaboration in an enterprise IT environment. It is designed to keep track of the chain of mail flow that are sent, replied, received or forwarded from Microsoft Outlook and received at the client-side Microsoft Exchange Server, before being routed to the target destination client. With the help of the adapter, the tracked mails can be identified and can be synchronized across disparate ALM tools connected in an integrated setup. Integration of the Exchange Server with other ALM tools using the adapter facilitates entity and field mappings, which ensure full data flow across tools.

Features & Benefits

  • Integration facilitates easy and time-saving ways to track email conversations.
  • Incoming emails automatically appear in the connected tool based on criteria.
  • With email tracking, you’ll get real-time notifications as soon as a prospect opens your email. You will also be notified if any of the links have been clicked on, thereby making it easier to follow up.

Benefits of Microsoft Exchange Server Integration Adapter

  • Automatic capturing of mails as Ticket: The adapter when integrated to Kovair Omnibus Platform can route mails based on the criteria to the connected tools—like ServiceNow, Jira, RTC, etc—for creating tickets automatically. Moreover, with the power of omnibus once the ticket are added an automatic mail can fired to the sender for acknowledgment. Acknowledgement mail can also contain URL of the ticket added.
  • Email Data: The adapter can expose Email data as an Item for the connected ALM tools along with attachments. Adapter with the power of Omnibus allows parsing and processing of email content and converting the same into attribute values.

Services Supported in Kovair Microsoft Exchange Server Adapter

Entities Exposed Supported Events Supported Actions Exposed Relations
  • Email
  • Supports basic events like Add and Modify.

Note: Modification of sent email is not possible. However, replying to an email effects last modification time of the sent email, to capture such events modify event is exposed.

  • Supports basic actions like Add and Modify.

Note: if a modify action comes, then a reply will be created under that mail which is expected to be modified, instead of modifying an email. this reply will be sent to replyAll option of the mail. This may be controlled by the key “ReplyOnModifyAction” present in Web.Config of Adapter.

  • Email to Email. Cardinality Type is Many to Many.

Note: A reply or forwarded email will be taken as the related item. This reply will create a relation event. If the replied mail has a different subject (if subject is modified during replying) then a new conversation thread will be created in mailbox.

Use Case Scenario of Kovair Microsoft Exchange Server Adapter

To understand how the Kovair adapter for Microsoft Exchange Server works, let us consider a typical use integration scenario created between IBM RTC, Kovair ALM, and Microsoft Exchange, connected using Kovair Omnibus and Kovair adapter for Microsoft Exchange Server.

Use Case Scenario of Kovair Microsoft Exchange Server Adapter
  1. Emails sent from specific Microsoft Outlook and targeted to another specific Microsoft Outlook, will first be received at the client-side Microsoft Exchange server.
  2. Mails arriving at the Microsoft Exchange Server will then be routed to the target Microsoft Outlook that has been specified with the email id. If Microsoft Exchange Server is integrated to Kovair Omnibus with the adapter, then the mails will be generated and retrieved as Events by the adapter.
  3. If the RTC tool is integrated to Kovair Omnibus with Kovair RTC adapter, then these generated Events will be synced to the RTC tool as a work item.
  4. On successful synchronization, an acknowledgement mail notification will be sent back to the email id informing about the successful synchronization.
  5. Based on the information provided in the email content, the system should be able to parse the email bodies, following which the parsed values will be set as work item attributes. For example, if the email status has been set as “Importance = High”, then the value will be mapped as “High” under the Severity attribute of the work item in the RTC tool. In case if a mail contains an attached file, then the attachment will be treated as a relation event by the adapter and the same will be added as an attachment to the corresponding work item in RTC tool.
  6. If Kovair ALM is integrated to Kovair Omnibus using Kovair adapter for Kovair ALM, then all Work Items created or updated in the RTC tool will become automatically traceable from inside Kovair ALM.

Note: The adapter as developed and offered by Kovair follows the subject tool’s standard specifications. Any deviations from the Tool’s typical use pattern may not have been anticipated in our off-the-shelf product. For any customization or special configuration needs, please contact Kovair Sales – sales@kovair.com

Slack is a team collaboration tools that brings all your communication together in one single place. Team conversations in Slack can be organized into channels, based on teams, office departments, projects. Slack also allows users to share files, images, documents in different formats, add comments along with the shared files thus making collaboration more textual and transparent.

Kovair Slack Adapter

Kovair adapter for Slack helps to achieve integration scenario between Slack and other ALM tools, thereby enabling teams to collaborate, update and send notifications in real time across various channels. Integration with Slack using Kovair designed adapter enables team members to flow Channel records for individual entities into the target tool. Kovair Slack adapter ensures that all historical and current feedbacks are made available to each user with full context and in real time.

Features & Benefits

  • Easy flow of information enables team members to collaborate faster during high priority release, thus reducing communication cycle
  • Sends real-time notification to developers and testers.
  • Facilitates collaboration between team members geographically located across different regions.
  • Instant Build and Deployment status notification to the Operations team.
  • Bi-directional communication flow of comments for a given channel

Why Integrate Slack with Kovair?

  • Faster Collaboration: For high priority release, this can be a very useful integration where information can flow very fast without even opening the bug tracking tool.
  • Real-Time Notification: Developers and Testers are notified also real time. With Slack mobile app, they can check issue status on the go.
  • Geographical Scalability: This can more useful where teams are operating from two different geographical location and collaboration between two teams are tough.
  • Continuous Feedback: This can be very useful for DevOps scenario where continuous feedback is very necessary. Developer, Tester and Operations team can get notification and act very fast for each step.
  • Instant Build and Deployment Status Notification: Operations team can be notified immediately at any point of time that build and deployment is succeeded of failed. 
Entities Exposed Events Collected Actions Supported
  • Channel
  • Supports basic events like Add and Modify
  • Supports actions like Add and Modify

Use Case Example Of Kovair Slack Integration

Slack unifies your Projects team’s communication, thereby enhancing your project data flow. All the tools that you need are seamlessly integrated into a single Omnibus platform. To understand how Kovair Slack integration works, let us consider an integration scenario between Kovair Defect Management and Slack:

Example Of Kovair Slack Integration
  1. A consultant posts a Requirement in Kovair. The Requirement is added to Slack in the Requirement channel. The integration enables users to add comments against the Requirement, thereby enabling them to exchange feedbacks and information. Thus, further communication on the requirement can be done with the consultant and the Product Owner/ Manager through Omnibus Slack integration.
  2. Once the Requirement is finalized, the Product Owner can invite a Developer for the Job.
  3. All communication related to the requirement development can be done keeping the Developer and the Product Owner / Manager in loop through Omnibus Slack integration.
  4. Next, the Manage / Owner can invite the testing team to test it. Again, all the communication between the testing team and the manager can happen using the Omnibus integration.

Note: The adapter as developed and offered by Kovair follows the subject tool’s standard specifications. Any deviations from the Tool’s typical use pattern may not have been anticipated in our off-the-shelf product. For any customization or special configuration needs, please contact Kovair Sales – sales@kovair.com

QAComplete is a Test management tool that helps teams to effectively manage the entire testing process in your company and deliver high quality software by streamlining Test Management, Release Management, Tracking Requirements and Defects across all projects.

Kovair SMARTBEAR QAComplete Adapter

Kovair adapter for QA Complete helps to achieve an integration scenario between Defect management tools like SMARTBEAR QA Complete and other ALM tools. The adapter has support for two primary entities — Reviews and Defects. It supports synchronization of reviews and defects across other defect management tools and makes it more interactive through synchronization of review comments and attachments.

Features & Benefits

  • Web-Based codeless configuration screens for easy configuration and customization.
  • Centralized data view for multiple tool projects.
  • End-to-End Traceability View of the exposed entities and related data from SMARTBEAR QAComplete Tool.
  • Track relevant fields like ID, Title of defects and issues for each release.

Why Integrate SMARTBEAR QAComplete with Kovair

  • Centralized Data View of Multiple QAComplete tool projects:
    Users can synchronize data from multiple tool projects and view it from other ALM Tool interfaces.
  • Uniform Configuration for Multi-Tool Integration:
    Kovair QAComplete adapter can integrate SMARTBEAR QAComplete tools using a uniform Point-and-Click Configuration method guided by Kovair Interactive UI.
  • End-to-End Traceability of Data and Streamlined Reports:
    The adapter can expose entities and the data related directly from SMARTBEAR QAComplete tool to Kovair Omnibus. This makes the data visible from other ALM tools that are integrated to the Kovair platform thereby maintaining traceability from requirement to test case and from test case to requirement. Data visible from End-to-End Traceability can be leveraged to create custom reports, and analytics using Kovair reporting engine.
  • Direct Implementation of Actions: The adapter enables users to take direct actions like Add/Modify/Delete directly through Omnibus.

Supported Services in Kovair SMARTBEAR QAComplete Adapter

Entities Exposed Events Supported Actions Supported Relations Supported
  • Defect
  • Test
  • Test Step
  • Test Set
  • Requirement
  • Run
  • Run Step
  • Release
  • Supports basic object events like Add for all entities.
  • Supports basic object events like Modify for all entities except Run and Run Step.
  • Supports basic Attachment events like Add and Delete for all entities.
  • Supports basic Comment events like Add for all entities.
  • Supports basic object actions like Add for all entities except Test Step, Run, and Run Step.
  • Supports basic object actions like Modify for all entities except Test Step, Run, and Run Step.
  • Supports basic Attachment actions like Add and Delete for all entities.
  • Supports basic Comment action like Add for all entities.
  • Test to Requirement
  • Test to Test
  • Test to Defect
  • Test to Release
  • Requirement to Requirement
  • Defect to Defect
  • Defect to Requirement
  • Defect to Release
  • Defect to Test Set
  • Test Set to Test
  • Test Set to Release
  • Release to Requirement

Use Case Example of Kovair SMARTBEAR QAComplete Integration

To understand how the Kovair SMARTBEAR QAComplete Integration works, let us consider an integration scenario between tools QAComplete, TFS, and Kovair Application

With the help of Kovair Omnibus and Kovair adapters, the tools are integrated with each other thereby creating an integrated scenario. Below is a step-by-step scenario explaining how the tools work in the integrated scenario:

Kovair-SMARTBEAR-QAComplete-Integration
  • In QAComplete, a new requirement is added along with attachment under a project.
  • The Requirement will get automatically synced along with the attachment inside the TFS tool under the registered target project.
  • Now when a comment and an attachment are added against the Requirement from the TFS tool, these comment and attachment will get automatically synced under the Requirement in the QAComplete tool.
  • In case if a defect arises, then the user can create a new Defect from the QAComplete tool, with proper description and attachment. This Defect can be linked to the Requirement in QAComplete tool.
  • The newly created Defect will get automatically synced along with the description and the attachment as Defect in the TFS tool. The Defect will also get linked to the Requirement inside the TFS tool.
  • After the Defect has been resolved, the Developer updates the status to Resolved in the TFS tool; providing supporting attachment and comment under the Defect.
  • The updated status in TFS tool will lead to automatic change of status to Resolved in QAComplete tool. The supporting attachment and comment will also get synced under the Defect in QAComplete tool.

Note: The adapter as developed and offered by Kovair follows the subject tool’s standard specifications. Any deviations from the Tool’s typical use pattern may not have been anticipated in our off-the-shelf product. For any customization or special configuration needs, please contact Kovair Sales – sales@kovair.com

Jira is an issue tracking product developed by Atlassian for bug tracking, issue tracking, and project management. Installing Test Management plug-in ‘Test Management for Jira ‘enables Jira to Manage Test and Quality.

Kovair JIRA Test Management Adapter

Kovair adapter for JIRA Test Management helps to achieve an integration scenario between JIRA Test Management and other ALM tools, thereby enabling teams to manage their issues throughout the entire lifecycle.

Its primary objective is to enable teams manage and Test details. The Kovair adapter can help to fetch data from JIRA Cloud-related entities like Bugs, Epics, New Feature, Story, Improvements, Sub Task, Task, Custom Entities, Sprint, and Issue; as well as JIRA Test Management entities like Test Case, Test Step, Test Plan, Cycle, Test Run.

JIRA Test Management adapter offers support bi-directional synchronization of Custom Fields, System Fields, Attachment, and Comment for entity features namely for Custom Entities, Issues, and Sprint.

Features & Benefits

  • Web-Based codeless configuration screens for easy configuration and customization.
  • End-to-End Traceability View of the exposed entities and related data from Confluence tool.
  • Track relevant fields like Pages and associated comments and attachments.
  • Centralized data view for multiple spaces of Confluence.

Why Integrate JIRA Test Management with Kovair

  • Uniform Configuration for Multi-Tool Integration:
    With the help of a uniform Point and Click Configuration guided by Kovair Interactive UI, Kovair JIRA Test Management adapter can integrate JIRA Test Management tool to other ALM tools and create an integrated setup.
  • Centralized Data View for Multiple Tool Projects:
    Users can synchronize data from multiple tool projects and view it from other ALM Tool interfaces.
  • End-to-End Traceability and Streamlined Reports:
    The adapter can expose entities and the data related to it from JIRA Test Management tool to Kovair Omnibus. This makes the data visible from other ALM tools that are integrated to the Kovair platform. The same data can be leveraged to create end-to-end traceability, custom reports, and analytics using Kovair reporting engine.
  • Direct Deployment Actions: The adapter enables users to take direct actions like Add/Modify/Delete directly through Omnibus.
  • Adapter Service Support Details

    Entities Exposed Events Collected Actions Supported Relations Supported
    • Bug
    • Epics
    • New Feature
    • Story
    • Improvement
    • Sub Task
    • Task
    • Custom Entities
    • Sprint
    *Note: If ExposeIssueEntityOnly flag is set in web.config then only Issue Entity Exposed.
    • Basic Object events like Add and Modify supported for all entities.
    • Basic Object events like Delete is supported for all entities except Sprint.

    *Note: Delete events can only be fetched from JIRA Cloud only through Webhook. With Event Service the Delete event will not be exposed.

    • Basic Attachment events like Add is supported for all entities.
    • Basic Attachment events like Delete is supported for all entities except Sprint.
    • Basic Comment events like Add, Modify, and Delete are supported for all entities except Sprint.
    • Basic Relational events like Add and Delete are supported for all entities. 
    • Basic Object Actions like Add and Delete are supported for all entities except Sprint.
    • Basic Object Actions like Modify is supported for all entities.
    • Basic Attachment Actions like Add is supported for all entities.
    • Basic Attachment Actions like Delete is supported for all entities except Sprint.
    • Basic Comment Actions like Add, Modify, and Delete are supported for all entities except Sprint.
    • Basic Relational Actions like Add and Delete are supported for all entities.
    • Bug to Bug
    • Bug to Epic
    • Bug to Story
    • Epic to Bug
    • Epic to Epic
    • Epic to Story
    • Story to Bug
    • Story to Epic
    • Story to Story
    • Issue to Issue

    For JIRA Test Management

    Entities Relation Relation Field Events Supported Actions Supported
    Test Case Test Case to Epic Related Epic Add and Delete Add and Delete
    Test Case to Story Related Story Add and Delete Add and Delete
    Test Case to Bug Related Bug Add and Delete Add and Delete
    Test Plan Test Plan to Epic Related Epic Add and Delete Add and Delete
    Test Plan to Story Related Story Add and Delete Add and Delete
    Test Plan to Bug Related Bug Add and Delete Add and Delete
    Cycle Cycle to Epic Related Epic Add and Delete Add and Delete
    Cycle to Story Related Story Add and Delete Add and Delete
    Cycle to Bug Related Bug Add and Delete Add and Delete
    Test Run Test Run to Epic Related Epic Add and Delete Add and Delete
    Test Run to Story Related Story Add and Delete Add and Delete
    Test Run to Bug Related Bug Add and Delete Add and Delete
    Run Step Run Step to Epic Related Epic Add and Delete N.A.
    Run Step to Story Related Story Add and Delete N.A.
    Run Step to Bug Related Bug Add and Delete N.A.

    Use Case Examples Of Kovair Integration With Jira Test Management

    To understand how Kovair integration with JIRA Test Management works, let us consider an integration scenario with tools JIRA Test Management, Kovair Omnibus, and Kovair Application.

    • In JIRA, Test Cycle is a collection of Test Cases. Let us suppose that a user proceeds to execute a Test Case from JIRA Test Management tool.
    • Upon execution of each Test Case in a Test Cycle, a Test Run record will be generated. For every Test Run, a Run Step event will be generated depending on the number of steps present in a Test Case.  
    • A complete traceability of these records and results can be viewed directly from Kovair Application.
    • Kovair Omnibus works behind the scene and runs on an Engine Service. Based on the adapters registered, the mapping, and the service flow set, all details of the source tool and the target tool, along with the mapping details are stored inside Kovair Database. Whenever a record is triggered from the source tool, the service engine searches for the target tool details inside the Kovair Database and the fields against which the action is to be triggered in the target tool.
    • Now assuming that a Test Case upon execution in the JIRA Test Management tool fails. In that case, using JIRA Issue type, a bug can be created and linked with the Test Case, which can be viewed from JIRA Test Management under the Traceability Tab.
    • Users of Kovair application can get a complete traceability view of the events triggered by the target tool and the actions pushed to the target tool.

    Note: The adapter as developed and offered by Kovair follows the subject tool’s standard specifications. Any deviations from the Tool’s typical use pattern may not have been anticipated in our off-the-shelf product. For any customization or special configuration needs, please contact Kovair Sales – sales@kovair.com

    Jama is a popular requirements management solution that helps organizations with better and faster product definition and facilitates product delivery using Agile methods.

    Bamboo is a continuous integration and continuous deployment server developed by Atlassian.

    Kovair Intelligent DevOps is an enterprise level integration which enables automatic execution of Plan and monitoring real time metrics. This is achieved with seamless integration with Bamboo adapter— a continuous integration and continuous deployment server. Upon execution, Build and JobBuild data are collected in Kovair central platform for integration with other tools.

    Kovair provides a vendor neutral integration platform called Kovair Omnibus Integration Platform to which the best-of-breed ALM, and other tools can be integrated using adapters.

    Features & Benefits

    • Monitor and track Plan, Jobs, DeploymentProject Execution from Jenkins into Kovair ALM.
    • Execute Deployment from Kovair ALM central platform.
    • View the status of Builds from Kovair ALM or other integrated tools that are connected through Omnibus.
    • Direct navigation to Bamboo Interface from Kovair ALM to give the end users a complete 360-degree view.
    • Single interface for all continuous delivery pipelines of Jenkins.

    Kovair Bamboo Adapter

    Kovair adapter for Bamboo helps to achieve an integration scenario between Bamboo and other ALM tools. The adapter supports exposing the primary artefacts of Bamboo like Plan, Job, Job Build etc. These data are very much vital for any DevOps environment. The primary feature of the adapter is to execute Bamboo Jobs remotely from Kovair platform. The primary entities for which data can be fetched using Kovair Bamboo adapter are Plan, Job, Build, JobBuild, DeploymentProject, and Release. Moreover, Bamboo has a Built-in support for deployment Projects and Test Automation, thus with Kovair integration platform in-place creates a perfect deployment environment.

    Why Integrate Bamboo with Kovair?

    • Built-In Deployment Support: Continuous flow of builds to test environments and automatic release of builds to customers when the builds are ready, while ensuring that the links to issues and commits behind them are maintained.
    • Single-Click Deployment: The integration between Bamboo and Kovair ALM is a deep level integration. It enables users to avail single click execution of Plan from the ALM interface. Kovair with its rich integration adapter can extract pipeline as well as pipeline execution details to Kovair ALM

    Services Supported in Kovair Bamboo Integration

    Entities Exposed Events Collected Actions Supported Relations Supported
    • Plan
    • Job
    • Build
    • JobBuild
    • DeploymentProject
    • Release
    • Supports basic events like Add and Edit.
    • Does not support basic events like Delete.
    • Support for basic events like Comment is available only for entity Build.
    • Support for basic events like Attachment is available only for entities like Build, JobBuild, and Release.
    • Action is done using HTML field. “Run Plan” is the HTML field of Plan entity. When “Run Plan” is triggered, the plan is executed in Bamboo tool and a build is generated.
    • Plan to Job
    • Plan to DeploymentProject
    • Plan to Build
    • Plan to Job to JobBuild
    • Job to JobBuild
    • Plan to DeploymentProject to release

    Use Case Example Of Kovair Integration With Bamboo

    Trends like agile development, DevOps, and continuous integration has led to the modern enterprise’s need for building software hyper-efficiently.

    To understand how Kovair Integration with Bamboo 6.6.3 works, let us assume an integration scenario created by integrating tools like Eclipse, GitHub, SonarQube, Bamboo, and Kovair with Omnibus platform. Refer to the diagram below to follow how Kovair Integration with Bamboo works.

    Kovair Integration With Bamboo
    • After writing a code inside the Eclipse tool, the Developer runs a code analysis inside SonarQube.
    • If the code analysis is successful, then the code will get checked-in into a SCM like GitHub.
    • Since GitHub has a built-in integration with Bamboo, thus one can configure to execute the Plan to initate a build followed by deployment.
    • Results of successful executions inside Bamboo can be easily viewed from Kovair Application.

    Note: The adapter as developed and offered by Kovair follows the subject tool’s standard specifications. Any deviations from the Tool’s typical use pattern may not have been anticipated in our off-the-shelf product. For any customization or special configuration needs, please contact Kovair Sales – sales@kovair.com

    Confluence is a software program developed and published by Australian software company Atlassian to teams to manage contents and collaborate efficiently.

    Kovair Confluence Adapter

    Kovair adapter for Confluence helps to achieve an integration scenario between Confluence and other ALM tools. Using the adapter, records created in the Pages can be flowed into the target tool. With Kovair Confluence adapter, Attributes of a page — such as comments and attachments — can be bi-directionally synchronized.

    Features & Benefits

    • Web-Based codeless configuration screens for easy configuration and customization.
    • End-to-End Traceability View of the exposed entities and related data from Confluence tool.
    • Track relevant fields like Pages and associated comments and attachments.
    • Centralized data view for multiple spaces of Confluence.

    Why Integrate Confluence with Kovair?

    • Centralized Data View of Multiple Confluence tool projects:
      Users can synchronize data from multiple Pages of a space and view it from other ALM Tool interfaces or can be view from Kovair ALM.
    • End-to-End Traceability of Data and Streamlined Reports
      The adapter can expose entities and the data related directly from the Confluence tool to Kovair Omnibus. As a result, the data is also visible from other ALM tools that are integrated to the Kovair platform thereby maintaining complete traceability of data.
      Data visible from End-to-End Traceability can also be leveraged to create custom reports, and analytics using Kovair reporting engine.

    Services Supported in Kovair Confluence Integration

    Entities Exposed Entity Features Supported Events Supported Actions Field Syncback
    • Page
    • System Fields
    • Attachments
    • Comments
    • Supports Object Events like Add and Modify.
    • Supports Attachment Events like Add and Delete.
    • Supports Comment Events Like Add, Modify, and Delete.
    • Supports Object Actions like Add and Modify.
    • Supports Attachment Actions like Add.
    • Supports Comment Actions Add and Modify.
    • ID

    An Example of a Use Case Scenario between Confluence and SharePoint

    To understand how the Kovair Confluence adapter works, let us consider an integration scenario between tools Confluence and SharePoint.

    Use Case Scenario between Confluence and SharePoint

    With the help of Kovair Omnibus and Kovair adapters, the tools are integrated with each other thereby creating an integrated scenario. Below is a step-by-step scenario explaining how the tools work in the integrated scenario.

      Assuming Confluence as the source tool and SharePoint as the target tool:
    1. A Page is added along with attachment under a Space in Confluence.
    2. The Page data will automatically get synced to the SharePoint, registered target site. In addition, the SharePoint ID will automatically be synced back to Confluence.
    3. Now if a Page is modified with Attachment under a Space in Confluence, the modification will be automatically synced in SharePoint target Site.
    4. If the Page is again modified and an attachment is added under the registered Site in SharePoint, the modifications along with the attachment will be automatically synced to Confluence Target Page under the registered target Space.

    Assuming Confluence as the target tool and SharePoint as the source tool:

    • A Page is added with an attachment under a Site in SharePoint.
    • The Page will be automatically added to Confluence under the registered Target Space. Along with the Page, the Confluence Page ID will also get automatically synced back to SharePoint.
    • The Page with attachment is modified under a Site in SharePoint.
    • The modified Page with attachment will be automatically updated in Confluence under the registered Target Space.
    • The attachment of the Page is updated under the registered Space in Confluence.
    • The attachment of the Page will be automatically updated under the registered Site in SharePoint.  

    Note: The adapter as developed and offered by Kovair follows the subject tool’s standard specifications. Any deviations from the Tool’s typical use pattern may not have been anticipated in our off-the-shelf product. For any customization or special configuration needs, please contact Kovair Sales – sales@kovair.com