logo ganttlab icon


Releasing version 0.2.0

Published May 3, 2020

Now using milestone start date for issues, and generating 95.63% smaller CSS.

Releasing version 0.2.0 illustration

It's already started! Thanks to direct users feedback and the great reboot announced a few days ago, GanttLab is out with a new version labeled 0.2.0.

Your milestone start date

Generating a Gantt chart over your GitLab or GitHub issues is totally automated in GanttLab, without any configuration needed. Yet, you have maximum control over start and due dates through the GanttStart and GanttDue values placed right in your issues description. This lets you build the Gantt chart that exactly fits, and accurately describe your project schedule. Today, we are introducing a new feature which will greatly help you bootstrap your work to come through issues and milestones.

While you flush out your next weeks/months of tasks in issues, you'll most likely group those issues in a few milestones for increased visibility over your workflow. Setting a start date on your milestones now automatically applies that start date for your Gantt chart to all of the issues in this milestones. You still have the ability to apply a specific GanttStart to each of your issues, but instantly get a more precise Gantt chart without getting into too much details at those initial planification steps.

GanttLab issue start date from milestone

This new behaviour is already used in the ganttlab/demo project, and has been documented in the updated How it works section. It will only work with GitLab projects' milestones, as you can't set a start date on GitHub milestones (yet?). You can read more about this feature right on the issue that lead to it.

Improving performance

GanttLab page load time is extremely fast: 0.91 second, which is just under a second on average for all pages and sections of the application, from any user, anywhere in the world. One of the biggest downloadable resource was CSS styles, up until today when PurgeCSS got enabled to remove all of the unused CSS upon build.

With the latest Tailwind CSS v1.4, PurgeCSS has been tightly integrated to search for CSS classes used in files making for the application, which helps automatically removing any class - and all of its related code - from the final built package. For GanttLab, that represented a drop from 106.24 KiB down to 4.64 KiB for the whole, Gzipped CSS code!

Happy (faster and easier) Gantting!

GanttLab: The easy to use, fully functional Gantt chart for GitLab and GitHub.

© 2016-2021 Pierre-Alexandre Clorichel
All rights reserved