Feature Requests
Suggest improvements, share insights, and vote on features you’d like to see next.
Recent
-
Feature Requests
Group by Custom Field
In the Board view, I would like the ability to group by a custom field value. I want to be able to quickly brain dump tasks and have some sort of indicator that certain tasks are related to each other, like a tag or a folder.
-
Feature Requests
Critical Path filter
It would be helpful to be able to filter tasks by Critical Path. Also to have something in the 'get task' API response that indicates if the task is critical path.
-
Feature Requests
Dark mode
I often use GanttPRO in the evening and the bright interface can be hard on the eyes. Are there any plans to add the dark mode?
-
Feature Requests
How do you keep large Gantt chart exports readable?
I often export Gantt charts for client plans and presentations, but when a project is long or includes many tasks, the final PDF or image becomes difficult to read. I’ve tried adjusting the date range, zoom, task name placement, and visible fields, but I still haven’t found a setup that keeps the chart clear without removing too much detail. Has anyone found a combination of export settings that works well for large projects? Could you share how you set up your exports and whether there are any additional settings you feel are missing?
-
Feature Requests
Smarter workload conflict resolution across projects
Users managing several projects can identify overloaded resources, but deciding which assignment should take priority and how work should be moved is still largely manual. This becomes more difficult when deadlines shift and the same person is involved in several projects. It would be useful to set project or task priorities and receive suggestions for reassigning or rescheduling work across projects, with every change reviewed before it is applied. Which rules should guide those suggestions – deadlines, task priority, existing assignments, or resource availability? Would you prefer recommendations only or optional automatic balancing?
-
Feature Requests
Native Earned Value Management (EVM)
It would be very useful to have native Earned Value Management (EVM) capabilities directly in GanttPRO, without having to export project data to Excel or other external tools. Ideally, GanttPRO should use the project baseline, planned schedule, task progress, actual costs and a selected status date to automatically calculate the main EVM values and performance indicators, including Budget at Completion (BAC), Planned Value (PV), Earned Value (EV), Actual Cost (AC), Schedule Variance (SV), Cost Variance (CV), Schedule Performance Index (SPI) and Cost Performance Index (CPI). It would also be valuable to include forecasting metrics such as Estimate at Completion (EAC), Estimate to Complete (ETC), Variance at Completion (VAC) and To-Complete Performance Index (TCPI). These indicators should ideally be available both at task/work-package level and aggregated at project level, with the possibility of analysing performance at a selected reporting or status date. An EVM dashboard would also be extremely useful, including S-curves for PV, EV and AC over time, together with the main cost and schedule performance indicators and forecasts. This would make GanttPRO much more suitable for structured project performance control, allowing project managers to assess not only whether activities are late or on schedule, but also how much value has actually been earned against the approved baseline, how efficiently time and budget are being used, and what the expected final project performance is likely to be.
-
Feature Requests
Custom colors
I’d love to be able to choose custom colors for tasks and projects. The current palette is a bit limiting, especially since our team already has its own color-coding system. Thanks!
-
Feature Requests
More predictable scheduling around dependencies
It would be very useful to have more predictable and consistent scheduling behaviour for tasks linked by dependencies, especially when task dates are recalculated across weekends or other non-working days. At the moment, when dependent tasks are moved or automatically rescheduled and their dates cross a weekend, the task duration can sometimes increase by one working day, even though the task itself has not changed. Ideally, GanttPRO should preserve the original task duration expressed in working days and recalculate only the start and finish dates according to the assigned working calendar. For example, a five-working-day task should remain a five-working-day task regardless of whether it starts on a Monday, a Thursday, or is shifted by a predecessor across a weekend. Dependency-driven rescheduling should therefore behave deterministically and consistently, taking into account working days, weekends, holidays and the selected project or resource calendar without unintentionally altering task duration. This would make schedule changes much easier to understand and control, especially in projects with long dependency chains, where even a one-day unintended increase in duration can propagate through several successor tasks and affect the overall project completion date.
-
Feature Requests
Better scaling for printed Gantt charts
When printing larger project plans, Gantt charts can become too compressed and difficult to read. Better scaling and layout options would be useful, especially when printed plans need to be shared with colleagues or stakeholders.
-
Feature Requests
More structured reporting for progress, costs, and time tracking
Hi everyone, I’ve been using GanttPRO mainly for planning, but when it comes to tracking progress and performance, I feel like something is missing on the reporting side. For example, it would be really helpful to have a more structured view of: planned vs actual progress, cost deviations, time spent vs planned. Right now it’s a bit hard to analyse this across projects in a clear way. Would be great to have more detailed reports or table-based views for this. Curious if there is anything available now?