Overview

TeamForge EventQ is a TeamForge capability that provides traceability for product life cycle activities such as work items, SCM commits, continuous integration (CI) builds, and code reviews.

Problem statement and Solution

Organizations currently tend to have modern mixed-vendor, heterogeneous environments with complex lifecycles including work item, commit, review, build/test, deploy, and other tasks that are monitored or managed by stand-alone tools. The tools may be vendor-supplied or open-source, and may reside on-premises or in private, public, or hybrid clouds. These tools, however, lack the ability to associate with one another and do not lend themselves to end-to-end traceability: organizations cannot easily see the connections between activities derived from disparate lifecycle tools. Yet to achieve traceability, organizations are often forced to use an all-in-one, monolithic solution that excludes popular point tools. TeamForge EventQ offers a traceability solution that preserves the advantages of your best-of-breed tools.

While TeamForge EventQ is extensible, this version provides the following packaged adapters for connecting lifecycle activities:

Table 1. TeamForge EventQ Packaged Adapters
Type of service	Products
SCM/Version Control	Git, Subversion
Code Review	ReviewBoard, Gerrit, Atlassian Crucible
Build/Test	Jenkins, JetBrains TeamCity
Issue Tracker	CollabNet TeamForge, Atlassian JIRA

TeamForge EventQ Vision

In a modern and frequently fractured development environment employing tools from different vendors, TeamForge EventQ aims to provide:

Aggregation — Using packaged adapters and an extensible architecture, TeamForge EventQ obtains and stores metadata about key lifecycle activities like work items, commits, builds/tests, and code reviews across vendors and platforms.
Traceability — TeamForge EventQ draws associations between activities across the entire lifecycle and enables traceability through the various steps or stages of the lifecycle.

Feature overview

TeamForge EventQ aims to aggregate lifecycle metadata across various tools and establishes networks of associations across those lifecycle activities. The use cases for TeamForge EventQ include visibility into development activities, visibility into associations between lifecycle activities, and requirements traceability for auditing purposes.

Activity Streams: Activity streams provide a "project chronology" showing the most recent activities at the top and the oldest at the bottom. See Activity Stream for more information.

Extensibility

While TeamForge EventQ ships with some adapters, its extensibility ensures that users can write custom adapters to extend TeamForge EventQ to other work item trackers, version control, CI, and code review systems. New product classes may also be extended using Extensible Data Sources (XDS). See Extending TeamForge EventQ for more information.