GForge 22.0 Released!

GForge v22.0 is primarily a feature release with a fair number of bug fixes included

Introducing Planning Boards

You already know GForge allows you to plan, distribute and track your work. With GForge you are already able to plan a release, break the release down into manageable sprints and assign work to your team. Planning Boards gives our existing kanban features a big shot in the arm by allowing you to create boards and quickly begin moving work around. The image below gives an example of moving tickets in a release into sprints and assigning the work out.

We’ll be sharing a deeper dive covering Planning Boards on here and on our YouTube Channel.

Other Key Highlights in v22.0

Project Navigation – We’ve made a big improvement to the project navigation bar. The new version now groups related project features and adds labels. The prior version assumed you knew the icon for each feature).

  • Tickets
    • There are cases where you want to have tickets in one project reference commits made in other projects. The commits tab in the ticket editor will now show the commit data.
    • There is a printable version of a ticket.
  • Documents – You can now add tags to documents.
  • Version Control – There’s been a number of improvements:
    • For Git repositories we’ve replaced the “master” branch with the name “main” (this only applies to new projects)
    • We’ve added a script to convert CVS repositories to Git
    • Some minor bug fixes (see ChangeLog below for more information)
  • Admin:
    • We now have the ability to share a software bill of materials (SBOM) listing all the libraries and packages GForge uses in each release. You can request the SBOM by email feedback@gforgegroup.com
    • Projects can now to exported from one GForge instance and imported into another GForge instance assuming both instances are running the same version of GForge.

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

Check back soon as we’ll be sharing our plans for the rest of 2022!

Download GForge 22.0 Now!

Take a tour of GForgeNext!

Getting Started with GForgeNext

GForge 21.2 Released!

GForge v21.2 is primarily a bug fix release. You will notice that there aren’t that many tickets in this release because we continued to focus on core technologies (libraries, etc) that needed to be upgraded. Specifically, a lot of energy was focused on upgrading to Angular 1.6.

Highlights in GForge 21.2

  • OIDC Support – GForge now supports OIDC and works with SSO systems like Okta.
  • Site Search – When inside a project, the navbar search now allows a way for you to search outside the current project (i.e. across all your projects and their artifacts)
  • Reports – There’s a couple of new reports for Site Administrators including a Cron History and Audit Log Reports.
  • Site Administration – We’ve added data retention settings for purging cron history and activity log data.
  • Kanban – The user interface has been completely revamped when working with tickets in Kanban view.
  • SVN – There’s been a number of improvements. The most notable is we’ve improved the speed of SVN operations (especially repositories with a lot of files). Also for repositories using SSH we fixed an ACL issue.

The 21.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 have officially dropped support as of October of 2020. We will still answer any support questions about older releases but we will not be providing any future code updates or patches. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.

Check back soon as we’ll be sharing our plans for the rest of 2022!

Download GForge 21.2 Now!

Take a tour of GForgeNext!

Getting Started with GForgeNext

GForge How-To: Project Admin SCM Settings

Hello and welcome to another GForge How-To. In this series, we teach you tips and tricks to help you maximize your experience with GForge. This time, we’re talking about the Project Admin SCM page, and the settings available there.

The settings on this page are as follows:

Access Method toggles between accessing your SCM over SSH or HTTPS; SSH is the default.

Git LFS support enables and disables Git LFS support.  

Code search indexes the code in your promotion model branches for searching.   Code tagging indexes the project’s code to tag related tracker items and user commits.  

Enable Anonymous Read allows SCM to be read by anyone, including anonymous users.  

Associate Tracker Items has three choices: you can keep commits unattached to tickets, attach them when you want, or require that every commit associates to a ticket.  

Restrict Tracker Item Associations requires commit ticket IDs to reference a ticket in the project.  

Commit Notifications sends an email to everyone monitoring the SCM repo when someone commits.  

Validate Committers ensures that each commit is pushed by an authenticated user.  

Validate Assignment automatically assigns a specified ticket to a committer.  

Access Text shows any text you type in on the main SCM repo page.  

Browse Text shows the text you type on the SCM Browse page.

As you can see, the SCM settings available to project admins can help in customizing and correcting GForge to fit any project’s needs. If you have any questions or feedback about the Project Admin SCM page, you can send us a message here. Make sure to check your inbox for more GForge How-To’s in the future!

GForge 21.0 Released!

We’re happy to announce the immediate availability of GForge 21.0. This is largely a feature release with a number of bug fixes sprinkled in..

Highlights in GForge 21.0

  • Tickets: You can now create and update tickets using a CVS.
  • Tickets: Go to any ticket you have access to using the # in the search bar (e.g #1234)
  • Tickets: When saving a ticket, all validation errors are shown in a modal window.
  • Tracker: You can create reports that filter using keywords, tags and submitter.
  • Documents: You can now upload entire folders (drag-n-drop supported)
  • My Reports: We made major improvements to the scalability and speed when running large reports.
  • Releases: We added a new Downloads report. GForge was already tracking the download data so this will work for all existing projects.
  • Git/SVN/CVS: You can now share links directly to files in the GForge interface (authentication/authorization checks are performed).
  • Git/SVN/CVS: You can now require a commit message without having to require a ticket number.
  • LDAP: We now ship a script that will disable GForge accounts for users no longer in LDAP.
  • We have published the “Tour” button content for any pages that had no content.

The 21.0 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 have officially dropped support as of October of 2020. We will still answer any support questions about older releases but we will not be providing any future code updates or patches. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.

Check back soon as we’ll be sharing our plans for the rest of 2021!

Download GForge 21.0 Now!

Take a tour of GForgeNext!

Getting Started with GForgeNext

GForge 20.2 Released!

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

Highlights in GForge 20.2

  • Large File Uploads – GForge now implements chunked uploading which allows you to upload files in up to gigabytes in size, if desired. This has been implemented anywhere file uploads are allowed but specifically for Docs, attachments to tickets, releases and for importing SVN dump files. (Note: there are a few settings you must set to achieve this).
  • Docs – You can now upload and an extract a zip. This is great for moving a large number of files.
  • French Translation – 20.2 now support French in addition to English and Spanish.
  • Organizations – There have been a large number of improvements to organizations. Key changes include:
    • Organization homepage gets a facelift which includes showing all the projects in the org and GForge shows how many users in your organization and the disk usage across all projects.
    • You can create a project from the organization homepage which ensures the project is properly related to the org.
  • WYSIWYG – Now uses local storage to help prevent loss of edits.
  • PostgreSQL 13 – GForge now support PostgreSQL 13. The upgrade process will give you the option of making the switch or staying with PostgreSQL 9.
  • DevOps – A number of important improvements to the GForge environment have been made to improve overall availability. These changes will be transparent to you but if you contact us we’d be happy to share them.

The 20.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 have officially dropped support as of October of 2020. We will still answer any support questions about older releases but we will not be providing any future code updates or patches. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.

Download GForge 20.2 Now!

Take a tour of GForgeNext!

Getting Started with GForgeNext

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