TeamForge: An Essential Cog Driving CloudForge

June 12, 2013 Patrick Wolf

Recently, we opened up our CloudForge platform to allow unlimited free TeamForge projects; previously only available to CloudForge Agile Enterprise subscribers. This alone represents a big leap forward in the functionality available within CloudForge: issue tracking, document storage, wiki, and discussion forums within a single platform integrated with subversion and Git. However, we also took this opportunity to make a few sizable changes in our implementation of TeamForge to better integrate TeamForge with CloudForge and improve your user experience.

The first new feature that users will encounter is single sign-on (SSO) between CloudForge and TeamForge. Whereas CloudForge has been the administrative interface to manage projects, services, and users, TeamForge was the project workspace to track issues, share documents and collaborate. Now there is a single entry point for both, when a user logs into CloudForge he or she is also logged directly into TeamForge as well and can access all of the organization’s projects – based on their roles and permissions, of course. Users can also bookmark project pages anywhere in TeamForge and land on those pages after authentication. All of this obviates the need for separate interfaces to administrate projects and to perform day-to-day tasks within a project.

In the vein of UI consolidation, CloudForge’s TeamForge has a new look and feel giving a more uniform appearance across the platform. Utilizing the branding capabilities and the integration data services of TeamForge we were able to quickly customize TeamForge with an entirely new CSS, updated images, and new CloudForge-specific menu items. Anyone who has used TeamForge in the past, either within CloudForge or as a standalone ALM platform, will notice the differences immediately. Some of these changes are a teaser of things to come when TeamForge 7.0 releases later this year.

Although we think TeamForge looks much better now, our changes weren’t limited simply to the appearance of TeamForge; we also added some new features to TeamForge completely unique to CloudForge. Features such as integrating the CloudForge Activity Stream into the TeamForge project workspace and adding a quick-link menubar item for submitting new tracker artifacts.

TF Interface

The new TeamForge look and feel with integrated activity stream and quick link to submit issues.

Features like this can make the life of end users much simpler and are fairly trivial to implement in TeamForge. In fact, for any TeamForge customers who want to add a menu option in their projects to quickly submit new artifacts, here is the source code:
Within the the menu_bar.vm of the TeamForge Look Project add:

#if (${menuBar.currentProjectPath})
  <li class="dropdown"><a class="dropdown-toggle" href="#">
  Submit Artifact
  #if ($!API50.sessionKey)
    <ul class="dropdown-menu">
    #set ( $trackers = $API50.trackerApp.getTracker2List($API50.sessionKey, $PAGE_INFO.projectId).getDataRows())
    #if ( $ARRAY.length($trackers) > 0)
      #foreach ($tracker in $trackers)      
       <li class="dropdown">
       <a href="${LINK.getPageUrl(${menuBar.urlBase},">$tracker.title</a>
      <li class="dropdown">No Trackers Available</li>

Overall, we are pretty happy with how things have progressed so far but we are far from done improving our offering of both CloudForge and TeamForge. We hope that you will test it out and send us some more feedback so we can continuously improve.

Previous Article
Strides in Federated ALM-Mahindra Satyam and TeamForge 7.0 to the Rescue
Strides in Federated ALM-Mahindra Satyam and TeamForge 7.0 to the Rescue

The software development community has struggled over the years with the debate between best-in-class tools...

Next Article
Adhoc AI Reporting & Downloads
Adhoc AI Reporting & Downloads

I wanted to share the results of a poc (proof of concept) effort i recently found success with using the ap...