GForge 20.1 Released!

GForge 20.1 Released!

We’re happy to announce the immediate availability of GForge 20.1. This is largely a bug fix release with a handful of new features.

Highlights in GForge 20.1

  • CloudForge Migration – With CloudForge shutting down on October 1st, you can now import CloudForge/TeamForge projects into next.gforge.com.
  • Thumbnail Generation – Office documents, PDFs and image files will have thumbnail images generated in tickets and in the document manager.
  • Workflow Locking – You can now lock tickets as part of a workflow transition.
  • Wiki Locks – You can now lock wiki pages.
  • Ticket Comments – You can now edit or delete your own comments on tickets.
  • WYSIWYG – Editor now elegantly handles content pasted from other sources (PDFs, websites, etc).
  • CVS – GForgeNext has added support for CVS to compliment the existing support for Subversion (SVN) and Git.

The 20.1 ChangeLog will help you understand the changes you can expect.

Just a reminder for customers still running GForge Advanced Server (v6.4.5 and prior) we are planning on officially dropping support in October of 2020. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.

Download GForge 20.1 Now!

Take a tour of GForgeNext!

Getting Started with GForgeNext

GForge 2020 Released!

GForge 2020 Released!

We’re happy to announce the immediate availability of GForge 2020 (aka 20.0). This is a large feature release and also includes a number of bug fixes.

Highlights in GForge 2020

Zoom Integration – You can now create Zoom meetings and invite project team members to the meeting right from GForge (SaaS only).

oAuth Support – You can now log-in to GForge using your Google account (additional oAuth providers will be coming).

Auto Tagging – When users push commits, GForge will now automatically tag the user, project and ticket with any technologies identified in the commit (e.g. Java, XML, JavaScript).

Code Search – GForge now indexes Git and SVN repositories allowing you to search your codebase right from GForge.

Git LFS – GForge now supports Large File Storage (LFS) for Git repositories.

DKIM Support – For on-premises customers, GForge now supports DomainKeys Identified Mail (DKIM) which adds additional email security and SPAM protection.

The 2020 ChangeLog will help you understand the changes you can expect.

Just a reminder for customers still running GForge Advanced Server (v6.4.5 and prior) we are planning on officially dropping support in October of 2020. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.

Download GForge 2020 Now!

Take a tour of GForgeNext!

Getting Started with GForgeNext

GForge joins other tool makers in offering wares for free to help companies collaborate during the Coronavirus

NOTE: This article was originally published Computerworld

Major collaboration and video conferencing software vendors are now offering products to users for free in response to the spread of the coronavirus. 

Concerns about the COVID-19 virus have led to a worldwide boom in remote working, as organizations encourage or require employees to stay home and cities, states and even some countries go on lockdown. 

While many companies have seen their stock prices take a battering due to disruption caused by the virus, some software vendors that enable remote work, such as videoconferencing software provider Zoom, have seen their share value climb dramatically.

Read more…

How GForge can keep the coronavirus threat from killing businesses

NOTE: This post was originally published on Engineering 360, An IEEE GlobalSpec publication. View the original article here.

GForge is helping businesses adapt to the coronavirus threat by making it easier to use a collaboration platform

For organizations new to using collaboration platforms or new to GForge, the company is offering GForge in both software as a service (SaaS) or on-premises formats for free for up to 12 months. GForge can be installed on-premise in one minute, or users can get started instantly using the SaaS platform.

Both options provide:

  • A messaging system to help facilitate online meetings
  • Ways to plan, distribute and track teamwork
  • Document sharing and knowledge management
  • Team collaboration tools like integrated chat, notifications and email support

To support the teams that are suddenly transitioning to remote work, GForge is also offering the following on a complimentary basis:

  • Ability to identify the best hosting options for an organization.
  • Ability to configure GForge to conform to the processes of an organization.
  • One free online training session for users.
  • One free online training session for administrators.
  • Weekly reviews to ensure that teams are getting the most out of GForge.

GForge is used globally by large and small organizations, and most of its features can be used by any kind of team looking to put an affordable solution in place. To contact the author of this article, email engineering360editors@ieeeglobalspec.com

Big Changes Ahead for GForge in 2020

Big Changes Ahead for GForge in 2020

With 2020 well underway we are hard at work on a bunch of new features that will take your collaboration to the next level. Before we cover what’s in store, be sure to checkout a recap of the “Top 8 GForge Features from 2019” 

OAuth Support – Not only will GForge support OAuth, over time we will include support services like Google, ADFS and GitHub.

Conferencing Support – GForge will be looking to add support to conferencing solutions like Zoom.us and WebEx allowing you to launch meetings right from within GForge.

Auto Tagging – There’s a lot of information in a commit. In 2020 GForge will harvest information from commits to provide better analytics. For example, a commit including Java, Javascript and SQL changes will add tags with those technologies to both the project and the author. Similarly, GForge will tag individual tickets in the same manner.

Git Improvements – GForge will be adding Git Large File Support (LFS) this year allowing individual files of up to 2GB to be included as part of pushes.

GitHub Migration – GForge will allow you to import projects from GitHub into GForge which will migrate the Git repository and GitHub Issues.

Workflow Improvements – GForge will add webhook support to ticket workflows allowing for deeper integration. Additionally GForge will include support to lock tickets as part of the existing workflows.

Document Thumbnails – Anywhere you add documents in GForge including tickets, Docman, etc GForge will generate thumbnail images you can preview before deciding if you want to download them.

Survey of 2020 Features

Top 8 GForge Features in 2019

Top 8 GForge Features in 2019

It’s the end of February and while we are hard at work adding new collaboration features to GForge for 2020, this seems like a good time to quickly reflect on what was accomplished in 2019. To help set the stage here’s some raw numbers for you!

  • In total we added 138 new features to GForge.
  • 255 bugs were squashed
  • We pushed over 1100 commits

What’s missing in those numbers are the key accomplishments from 2019 so let’s take a moment to cover the top 8 features from last year!

  1. Dark Mode!
Screenshot of GForge in “Dark Mode”

We admit, while Dark Mode adds little in the way of true business value, those who use Dark Mode in other applications and spend a lot of time in GForge will appreciate this.

2. Sprint Retrospectives

Add a Retrospective to closed sprints.

When closing sprints in GForge you can now add a retrospective to document what went well, where problems arose and you can begin identifying the steps needed to make improvements going forward.

3. Automated Release Notes

Import Release Notes with the Click of a Button

When you close a release you can import a table of all closed tickets in the release and then edit the Release Notes before publishing them.

4. Service Desk

GForge Service Desk in Action.

We added the ability for you to add user groups to your projects. In addition to making access control easier, this means you can now use GForge as a Service Desk solution complete with email integration.

Other Key Features

In addition to the highlights above, there are a few other features from 2019 worth noting.

  • Authentication Improvements – Last year GForge added SSO support along with the ability for GForge admins to moderate new user accounts even when using LDAP or SSO.
  • Offline Installations – Need to collaborate on projects inside a protected network without outbound internet access? GForge now supports offline installs and upgrades.
  • Portfolio Management – You can now organize all your GForge projects to match your organizational structure. Not only does this improve analytics, now when you assign users to organizational units they will only have access to private projects within their organization (public projects are still accessible).
  • Subversion (SVN) Improvements – GForge now allows you to restrict access to specific paths in your SVN repository on a role-by-role basis. We also added code review support for projects using SVN.

As excited as we are about what we’ve accomplished in 2019, 2020 will bring a lot more collaboration features to the table. Whet your appetite by reading the “Big Changes Ahead for GForge in 2020”.

Use GForge Now with a Free Account!

Download GForge Now!

GForge v19.2 Released!

GForge's new Dark ModeWe’re happy to announce the immediate availability of GForge v19.2. This release includes three dozen new features and a number of bug fixes.

Download GForge v19.2 Now!

Take a tour of GForgeNext!

Getting Started with GForgeNext

Highlights in GForge v19.2

Dark Mode – GForge is joining the Dark Mode fray!

Project Groups – Project leads can now create groups of users and assign them a project role. Prior to this release only GForge admins could create groups.

Service Desk – With the addition of Project Groups, GForge can now be used to provide service desk functionality.

Improved Analytics – We’ve been listening and now we delivered. GForge now includes better analytics for better managing your projects and overall project portfolio.

Automated Release Notes – This version of GForge provides improved release management. Now when you complete a release you can, with the click of a button, generate release notes.

Better Navigation – While we’ve received a lot of positive feedback on getting around in GForge, we’ve answered calls to improve navigation.

The v19.2 ChangeLog will help you understand the changes you can expect.

Just a reminder for customers still running GForge Advanced Server (v6.4.5 and prior) we are planning on officially dropping support in October of 2020. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.

Download GForge v19.2 Now!

Why Does Collaboration Software Suck?

Why Does Collaboration Software Suck?

Let’s face it, the collaboration space has no shortage of options. Today’s solutions come in different flavors of SaaS, on-premises or hybrid, all promising you that a few mouse clicks will have you collaborating better. The one attribute most of them have in common is they suck. In fact, many of these solutions actually make collaboration worse. To help you navigate your options, let’s lift the hood and explore many of the common problems with today’s collaboration solutions.

Collaboration software shouldn't suck. Learn about some common problems to avoid.
  1. You Get Pieces & Parts 
  2. Too Small or Too Big, Won’t Scale 
  3. Who’s Working for Whom?
  4. Comments <> Collaboration
  5. They’re Expensive
  6. Golden Handcuffs 

You Get Pieces & Parts

Let’s face it, as a business grows so do your needs. This transition happens slowly and before you know it you look down to discover you have lots of little solutions each itching a single scratch in helping you collaborate better. Worse yet, navigating between those tools is often painful. In the best case the integration features adds even more buttons to an already complicated user interface. In the worst case you will have to manage a bunch of bookmarks to get to specific features. 

On the subject of user interfaces, today’s solutions are all over the board. Geek-centric solutions might make your IT teams happy, but could alienate your project managers, product managers and upper management. Some solutions create busy-work for team members so that management can have pretty reports.  Other solutions are too enterprise-y, trying to be everything to everyone, but making everything more complicated instead of more efficient. Their lack of focus makes the user experience painful – with too many links, buttons, and tables, all competing for your attention.

Finally, the lack of a comprehensive feature set makes portfolio management difficult, if not impossible. Some solutions focus on work (tickets, issues, tasks), some focus on the process (kanbans, CI/CD integration), and others focus on people (chat).  But what about the bigger picture?

  • How many projects do we have in flight? What’s the relative health of those projects?
  • Have we spread our valued team members too thin? 
  • How do I find quickly find what I’m looking for? How about searching all the things (projects, users, tickets, documents)?  Centralized searching isn’t something you can do without… – yep, you guessed it – buying another tool. 

Next, let’s discuss the insanity of help desk solutions. It’s common for projects to deliver solutions to customers who need access to a support team. Isn’t a ticket just a ticket? Why do vendors try to upsell a separate help desk solution? Under this model, if a customer raises an issue that requires remediation by your team you end up with two tickets: one ticket in the help desk solution and another ticket in the collaboration solution. In most cases there is no inherent association between the two.

Now let’s think about turnover. When someone leaves your organization, how easy is it to revoke their access? Even if you’ve identified the replacement for a departing team member, reflecting that change in multiple projects can be cumbersome. And, once again, if you’ve been upsold both of those processes become harder.

The final point worth considering is discoverability. This may sound ridiculous, but many solutions don’t allow you to specify who is able to discover a project in the first place. If you are doing real portfolio management then knowledge sharing is critical, and you should be able to specify who can discover projects. Similarly, you should have a way to explicitly limit discoverability to certain projects. 

Too Small or Too Big, Won’t Scale

Not all projects are created equal. Say that again: not all projects are created equal. In a world where organizations have dozens or even hundreds of projects, in various phases of development, support and retirement,  it’s important to be able to scale up or scale down features without the headache of buying more seats or finding a new solution.

Then there’s the SaaS/Cloud versus on-premises discussion. That decision should be yours and your choice shouldn’t make deployment and management any harder. There’s no shortage of on-premises solutions, yet many require painful, complex installation and upgrade processes. Given the critical role collaboration solutions play, getting them up and running (and keeping them up-to-date) needs to easy. Many of these solutions cannot be installed at all without  an internet connection for the server. This means installing a collaboration solution on your super secure network will be difficult if not impossible.

Then, once you are up and running, how do you control access to your projects? Access control varies greatly between collaboration solutions. Large projects often have large teams, with technical, management, and stakeholder members, each playing a role in successful delivery. Believe it or not, some collaboration solutions don’t allow you to define your own roles, instead, imposing a set of roles often giving users access to either too many or too few features. Roles are a key in any real collaboration solution and are often reusable, specifying the level of access users have. And even if you can specify roles on your project, if you’ve been upsold you may well be stuck having to manage access to each upsold feature separately.

This is where the tools start to run the team. What started out as only a ticketing solution soon includes a wiki, chat, help desk and next thing you know, you are looking at a bunch of tools, held together with duct tape and web hooks, none being the authoritative source of your precious project data, and all individually imposing different ways for you to get your job done. When will this nonsense stop?

Who’s Working for Whom?

That question may sound absurd but, yes, we are asking that question with a straight face. Are your tools working for you or you having to bend to their will? To illustrate, let’s start with something as basic as ticketing. Tickets are the atomic unit of work by which things get done. All your planning, distribution and tracking of work happens through tickets. In fact, most of your collaboration will be centered on the best ways to deliver the work outlined in a ticket. So why do so many systems get the most important, fundamental needs all wrong? Let’s answer that by identifying common shortcomings of many collaboration tools:

  • Duplicate Tickets – When creating a ticket should the system let you know you may be submitting a duplicate? Furthermore, shouldn’t the system give you hints that maybe the problem or goal in a ticket has been addressed already on sites like StackOverflow?
  • Batch Updates – Updating multiple tickets in batch should be easy to do. Yet many systems either don’t allow for this or make this far more difficult than it should be.
  • Quickly Adding New Tickets – In the planning phase, it is common to create multiple tickets at once all within the same milestone or sprint. Most systems require you to rekey many of the same pieces of data instead of using sane defaults.
  • Ticket Types – While the distinction about tickets is important (e.g. user story, epic, task, bug), adding flexibility shouldn’t slow the team down or make things more complicated..
  • Imposing Workflow – Workflow can help teams stay on track and handle tasks in a consistent way.  But your ticketing solution shouldn’t force a specific workflow on your team..
  • Dependencies – Dependencies between tickets is common. Solutions should make establishing blocking/non-blocking or parent-child dependencies easy and obvious.
  • Spam – Getting notifications that a ticket, sprint, epic or milestone has been changed is great, but do you really have to get a separate email for each update? Solutions should provide the option of receiving daily digests. 
  • Ticket Previews – Because the work in tickets can be a part of any milestone, release, sprint, etc you often need to know more detail than just the ticket number and summary. Yet, surprisingly, many solutions don’t give you ticket previews everywhere and every time tickets are referenced.

Comments <> Collaboration

Repeat after me: “Comments aren’t collaboration”. Don’t get me wrong, commenting on a ticket, wiki page, or document aids in collaboration but it isn’t true collaboration. That’s why we’re seeing all sorts of chat solutions rushed to market. Chat solutions are great and often serve as the central hub of any successful project. Here again, the upsell issue bites us but in the case of chat, it is exacerbated. Chat conversations give concise context and often include references to key project artifacts (tasks, support tickets, documents). For those exact reasons, chat should be a foundational and well-connected component of any real collaboration solution, not an upsell. For example, with an upsold chat solution, when you add a new team member you also need to manually give them access to the corresponding chat rooms or channels. And remember that problem about centralized search? Did a teammate answer your question inside of a ticket, wiki or in the chat channel? Shouldn’t a real collaboration solution answer that question for you? Why should you have to run the same search in different places?

They’re Expensive

A common problem with many collaboration solutions is that their base functionality has a high price tag. And despite that high initial cost, they have a limited scope, implementing only a few well thought out features. Make no mistake, this is on purpose – vendors use this approach to get you to spend more money. They accomplish this in one of two ways:

  1. The Vendor Upsell –  Do you want to add a chat solution to that fancy ticketing system you bought? They have an app for that. Oh, now you want some sort of documentation/wiki solution? Yep, get out your checkbook. The problem with vendor upsell is it often creates more problems. On top of having to negotiate a new contract for each product, you are now on the hook for keeping all your shiny, new tools integrated.  Now this integration may not be an issue if you are all in on cloud-only solutions but as soon as you bring any of those solutions in house you are stuck with keeping them connected. 
  2. Marketplace Ecosystem – Some collaboration solutions get around their lack of features by offering a marketplace where third parties can offer you solutions that integrate with your vendor of choice. This has all the same problems as the vendor upsell but now you are adding another vendor to the equation which, on top of the pricing issue, it means the integrations are going to be more fragile and any breaks in compatibility puts you at the mercy of both vendors.

Golden Handcuffs

With collaboration solutions playing such a key role in Getting Things Done, the more you use them the more valuable they become. So what happens when you get to a point when you want to make a shift in how you collaborate? 

For example, there are a few reasons an organization may want to move from SaaS to on-prem or vice versa and while it isn’t common, it shouldn’t be impossible, either. And if it isn’t impossible to do, the odds are the work in accomplishing that isn’t trivial. Moves like this should not only be possible but relatively easy to do.

And then there’s our friend “vendor lock-in”. You should never get into a vendor relationship that you can’t easily get out of. The upsell models makes switching out solutions even more costly, time consuming and error prone. Worse yet, if you have independent vendor solutions each itching a specific scratch, then it means those integrations will break requiring more time to keep them in sync.

What’s Irking You?

It isn’t all doom-and-gloom when it comes to collaboration software, but a solution that is right for you NOW may not be able to grow with you in the future. To that end, it’s important to understand where many of today’s systems fall short, and make choices that balance where you are today, and where you want to go. Do you have a collaboration solution driving you crazy? We’d love to hear the reason why your collaboration solution sucks.

Small Iowa Tech Inked Deals with Microchip, GE, Raytheon, BAE and Siemens

Small Iowa Tech Inked Deals with Microchip, GE, Raytheon, BAE and Siemens

Despite the technology industry being hyper focused on the next great start-up darling, one small Iowa technology company has managed to quietly ink deals with tech giants like General Electric, Siemens, Raytheon, BAE Systems and Microchip. The GForge Group, Inc, based in West Des Moines, Iowa,, has built an impressive list of clients for their collaboration platform, GForge. According to President Tony Bibbs, the success of GForge can be attributed to thinking like their clients, making sure GForge provides them the right combination of collaboration features, itching unique enterprise needs and leveraging their size as a selling point.

Enabling Real Collaboration

While the collaboration industry has long been deployed at scale to the cloud, The GForge Group has gone back to focusing on their roots of on-premises collaboration. Microchip, a global provider of microcontrollers, mixed-signal, analog and Flash-IP circuits is using GForge to collaborate on multiple levels, addressing the unique needs of their disparate teams and customer base.  Specifically, Microchip uses GForge to:

  • Collaborate across internal Microchip organizational groups.
  • Collaborate internally on Microchip products and services.
  • Collaborate externally with Microchip partners and customers.

Microchip achieves these varied levels of collaboration by leveraging GForge’s portfolio management features which allow them to organize teams, projects and customers with varying degrees of visibility.

Another key feature of GForge is the fact it is an all-in-one solution which overcomes two key problems faced in the on-premises collaboration space:

  1. Ala Cart Features – Some collaboration solutions sell similar GForge features ala cart with each having its own pricing and requiring work to configure those features to work in unison. This approach is inflexible because it means you need to know what features each project needs ahead of time.
  2. Best-in-Breed Features – Other organizations, often times unknowingly and over time, end up buying multiple products from multiple vendors providing specific features. This approach shares the same inflexibilities of ala cart features from a single vendor but this also makes integration difficult, fragile and expensive. 

GForge’s all-in-one approach makes all features available to a project but gives its customers the flexibility of scaling with the project. At Siemens, for example, they enjoy the flexibility of taking a proof-of-concept, using a few GForge features, to a full scale, mature project that has expanded to use more of GForge’s capabilities.

The all-in-one approach is paying off because large organizations recognize that not all projects are created equal and with GForge scaling with their needs they are able to focus on their strategic goals without the hassle of renegotiating pricing when the needs of a project changes.

GForge Enables True Enterprise Collaboration

While GForge gives project teams modern collaboration features (like sprints, standups and team chat), it really shines when deployed across an enterprise. For example, General Electric (GE) uses GForge to manage over 16,000 global employees, all collaborating on GE’s vast array of products and services. 

With GForge, GE is also able to specify the export control classification of every GE project, to ensure export control policies and procedures are observed in a consistent, auditable manner.

Raytheon uses two key GForge features to elevate their collaboration. Within Raytheon, there are strict security boundaries between various programs. To address that requirement, Raytheon can quickly deploy a dedicated, isolated instance of GForge for each program, giving their programs the collaboration tools they need. For projects that don’t have the same security requirements, Raytheon has a shared GForge instance for managing their entire portfolio. GForge allows Raytheon to classify shared projects for reuse readiness,to ensure systems achieve a level of maturity before they are reused elsewhere. 

GE and Raytheon rely on unique GForge features to increase productivity and reuse, and manage regulatory requirements and project risk.

GForge Leverages Its Size

Make no mistake, GForge runs at scale, and it has to in order to support such large customers. According to Bibbs, however, GForge’s true value is the fact they are a small, privately held company: 

“Being a small company, we are much more agile and far more responsive to our customer’s needs”.

 Bibbs pointed to their unique support model noting that all GForge engineers also provide direct customer support. 

“Our size allows us to use this model which has the benefit of engineers getting feedback directly from customers. Nothing gets lost or miscommunicated like you often see with multi-tier support models.” 

Another small business benefit GForge brings to the table their customers have the ability to have a direct impact on the product road map. “Listen, there’s a lot of competition in our market and there’s some big fish in our pond. Our success is tied directly to our ability to listen to our customers and, to a large extent, let them drive the direction GForge goes.” Bibbs goes on to point out GForge, despite its size, has been in the collaboration business as long, if not longer, than most of their competitors.

GForge v19.1 Released!

Role-based ACLs for Git
GForge supports role-based ACLs for Git and SVN

We’re happy to announce our second GForge release for 2019 is available! v19.1 adds a number of new features and comes with a number of bug fixes.

Download GForge v19.1 Now!

Take a tour of GForgeNext!

Getting Started with GForgeNext

Highlights in GForge v19.1

Role-based ACLs for Subversion (SVN) and Git – GForge now supports role-based access controls for both Subversion (SVN) and Git. This means you can control what areas in your repository users have access to based on their role in the project. In SVN this means you can limit a roles access to certain paths in your SVN repository (e.g. write access to anything in /branches and read-only access to /trunk). For Git this works similarly where GForge allows you specify which specific branches a user has access to.

Code Reviews in Subversion (SVN) – Beginning with GForge v18.0, you could perform code reviews in Git just fine. GForge now supports the same functionality using SVN.

Embedded Video Support – You can now embed online videos in many places in GForge including tickets, wiki entries, project homepages, etc. This support is included anywhere where the GForge WYSISYG editor is used.

Commit Integrity – When it comes to commits GForge tries to stay out of your way. One example is you can associate a commit to any ticket that is part of a project you belong to but the ticket doesn’t have to reside in the same project. While that can be handy, in some cases you need deeper control so in this release we’ve added two features ensuring commit integrity:

    1. There is a new configuration option that will tell GForge to enforce the committer is currently assigned to the ticket associated with the commit.
    2. Another new configuration option will tell GForge to enforce the repository being committed to is the same project the associated ticket is part of.

The v19.1 ChangeLog will help you understand the changes you can expect.

Just a reminder for customers still running GForge Advanced Server (v6.4.5 and prior) we are planning on officially dropping support in October of 2020. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.

Download GForge v19.1 Now!