<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Feature Requests ]]></title><description><![CDATA[Suggest improvements, share insights, and vote on features you’d like to see next.]]></description><link>http://community.ganttpro.com/category/4</link><generator>RSS for Node</generator><lastBuildDate>Sun, 20 Sep 2026 15:44:26 GMT</lastBuildDate><atom:link href="http://community.ganttpro.com/category/4.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 04 Sep 2026 14:43:59 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[More predictable scheduling around dependencies]]></title><description><![CDATA[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.
]]></description><link>http://community.ganttpro.com/topic/80/more-predictable-scheduling-around-dependencies</link><guid isPermaLink="true">http://community.ganttpro.com/topic/80/more-predictable-scheduling-around-dependencies</guid><dc:creator><![CDATA[eugenio.marogna]]></dc:creator><pubDate>Fri, 04 Sep 2026 14:43:59 GMT</pubDate></item><item><title><![CDATA[Native Earned Value Management (EVM)]]></title><description><![CDATA[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.
]]></description><link>http://community.ganttpro.com/topic/81/native-earned-value-management-evm</link><guid isPermaLink="true">http://community.ganttpro.com/topic/81/native-earned-value-management-evm</guid><dc:creator><![CDATA[eugenio.marogna]]></dc:creator><pubDate>Fri, 04 Sep 2026 14:40:00 GMT</pubDate></item><item><title><![CDATA[Better scaling for printed Gantt charts]]></title><description><![CDATA[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.
]]></description><link>http://community.ganttpro.com/topic/79/better-scaling-for-printed-gantt-charts</link><guid isPermaLink="true">http://community.ganttpro.com/topic/79/better-scaling-for-printed-gantt-charts</guid><dc:creator><![CDATA[erich.langer]]></dc:creator><pubDate>Wed, 26 Aug 2026 13:32:08 GMT</pubDate></item><item><title><![CDATA[More structured reporting for progress, costs, and time tracking]]></title><description><![CDATA[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?
]]></description><link>http://community.ganttpro.com/topic/61/more-structured-reporting-for-progress-costs-and-time-tracking</link><guid isPermaLink="true">http://community.ganttpro.com/topic/61/more-structured-reporting-for-progress-costs-and-time-tracking</guid><dc:creator><![CDATA[Theo Arden]]></dc:creator><pubDate>Mon, 13 Jul 2026 11:23:00 GMT</pubDate></item><item><title><![CDATA[Reporting still feels limited for real project tracking]]></title><description><![CDATA[Hi all,
I like using GanttPRO for planning, but when it comes to actually tracking project performance, I feel like the reporting side is still a bit limited.
For example, I often need to compare planned vs actual time and costs across multiple projects, and it’s not always easy to get a clear overview without exporting data and working on it separately.
It would be great to have more built-in reporting options that make this easier directly in the tool.
Is anyone else running into this?
]]></description><link>http://community.ganttpro.com/topic/70/reporting-still-feels-limited-for-real-project-tracking</link><guid isPermaLink="true">http://community.ganttpro.com/topic/70/reporting-still-feels-limited-for-real-project-tracking</guid><dc:creator><![CDATA[Emma Carter]]></dc:creator><pubDate>Fri, 10 Jul 2026 11:42:00 GMT</pubDate></item><item><title><![CDATA[Visualisation: exporting]]></title><description><![CDATA[Hi community!
While responding to your reviews, I’ve noticed a recurring question: “How can I export my Gantt chart so that it looks clean and readable in PNG or PDF?”. Here are a few practical tips that might help:


Switch the View mode to “Touch”. This makes the chart more spacious and often improves readability. Also, on the export page, you can refine the output by setting a specific Date range – from the project’s start date to its end date.
[image: feda27654f168f1043a6b86ad1a94980.png]


Export your diagram in smaller time periods using the “Date range” filter.
For example: September =&gt; April, May =&gt; August, September =&gt; December. Breaking the timeline into segments can make long projects much easier to present and read.
[image: ef3f155e7a436d02ee7436ce0aa1c16c.png]


To improve the export experience further, I’d love to hear from you: what do you feel is currently lacking in GanttPRO’s export options, or what would make your PDF/PNG outputs clearer and more usable?
]]></description><link>http://community.ganttpro.com/topic/60/visualisation-exporting</link><guid isPermaLink="true">http://community.ganttpro.com/topic/60/visualisation-exporting</guid><dc:creator><![CDATA[Ana GanttPRO]]></dc:creator><pubDate>Sat, 04 Jul 2026 12:55:33 GMT</pubDate></item></channel></rss>